Integrating customer and/or merchant functionality with discoverable applications

ABSTRACT

Integrating buyer and/or merchant functionality with discoverable applications is described. In an example, applications associated with a service provider can be stored in a repository associated with the service provider. At least a part of an application of the applications is associated with a particular, discrete functionality. The service provider can determine context data associated with a user computing device and can select, based at least in part on the context data, the application from the applications, wherein at least the part of the application is to be surfaced on the user computing device. The service provider can cause a user interface associated with at least the part of the application to be presented via the user computing device, wherein the user interface enables a user of the user computing device to input data for enabling the particular, discrete functionality, and wherein a portion of the context data is used to customize the user interface for the user.

PRIORITY APPLICATION

This application claims priority to U.S. Provisional Application No.63/058,841, which was filed on Jul. 30, 2020, the entire contents ofwhich are incorporated by reference herein.

TECHNICAL FIELD

Applications implemented on user computing devices have been developedfor a variety of purposes, including business, social, payment, andother purposes. These applications provide a graphical user interface topresent data to users as well as allowing the users to interact with theapplications. Such applications (i.e., native applications) aregenerally downloaded, for example, for security and authenticationreasons, on the computing device if the user wants to use all of theembedded functionalities.

BRIEF DESCRIPTION OF DRAWINGS

Features of the present disclosure, its nature and various advantages,will be more apparent upon consideration of the following detaileddescription, taken in conjunction with the accompanying drawings. Thedrawings are not drawn to scale.

FIG. 1 illustrates an example environment for performing techniquesdescribed herein.

FIG. 2 illustrates an example process for selecting and/or surfacing aninstant application based at least in part on context data associatedwith a computing device.

FIG. 3 illustrates an example process for selecting and/or surfacing aninstant application based at least in part on context data associatedwith a computing device.

FIG. 4 illustrates an example process for selecting and/or surfacing aninstant application based at least in part on context data associatedwith a computing device vice.

FIG. 5 illustrates an example process associated with determining asequence of instant application(s) to surface via a user computingdevice.

FIG. 6 illustrates an example process for data persistence acrossdevices and/or applications executing on different devices.

FIGS. 7A-7I illustrate an example of presenting an instant applicationto enable a user to perform a worker-specific task.

FIGS. 8A-8I illustrate an example of presenting an instant applicationto enable a user to perform a worker-specific task.

FIGS. 9A-9H illustrate an example of presenting an instant applicationto enable a user to perform a worker-specific task.

FIG. 10 illustrates an example of a sequence of interactable elementsthat can be presented to enable a plurality of instant applications tobe executed in a particular sequence.

FIGS. 11A-11G illustrate an example of automatically downloading andauthenticating a pre-configured application through an interactableelement presented via a merchant computing device.

FIGS. 12A-12F illustrate an example of cloning and downloading apre-configured application through an interactable element presented viaa computing device.

FIG. 13 illustrates an example of performing a buyer-facingfunctionality via an instant application associated with an interactableelement.

FIG. 14 illustrates another example of utilizing an instant applicationto enable a buyer to provide a tip via their own computing device,redeem loyalty points, collect loyalty points, review and/or modify anorder and/or cart, pay with an application on the computing device.

FIG. 15 illustrates an example of utilizing an instant application toenable management and/or ordering of inventory.

FIG. 16 illustrates a plurality of interactable elements which canrepresent different items and/or bundles of items that can be orderedand/or purchased via a scan, read, or other interaction with individualof the plurality of interactable elements.

FIG. 17 illustrates a plurality of interactable elements which canrepresent different functionalities that can be availed to a user via acomputing device.

FIGS. 18A-18D illustrates a plurality of user interfaces associated withnotifications and/or data that can be presented via an instantapplication.

FIGS. 19A-19F illustrate an example where a user can utilize an instantapplication to order a stored balance card.

FIG. 20 illustrates an example process for nesting of application(s) orpart(s) thereof, within another application, or part thereof.

FIGS. 21A-21L illustrate an example of transitioning between nestedapplication(s) or parts thereof.

FIGS. 22A-22M illustrate an example process associated with ordering viaan instant application.

FIG. 23 illustrates an example process for accessing instant applicationdata via an application within which the instant application is embeddedor otherwise associated.

FIGS. 24A-24D illustrate an example of transitioning between a buyerapplication and another application, or part thereof, that is embeddedin the buyer application.

FIG. 25 illustrates an example process for causing data input via aninteraction with a user interface presented via an instant applicationon a computing device of a user to be presented via a user interfaceassociated with a subsequently downloaded application on anothercomputing device of the user.

FIGS. 26A-26D illustrate an example of creating a mock experience for auser.

FIGS. 27A-27G illustrate an example of sharing an instant applicationwith another user, for example as a referral.

FIG. 28 illustrates an example environment for implementing techniquesdescribed herein.

FIG. 29 illustrates an illustrative block diagram illustrating a systemfor performing techniques described herein.

DETAILED DESCRIPTION

Parts of applications can be executed on a user computing device quicklyand without a user needing to download the entire application onto theuser computing device. That is, a part of an application can includeinstructions (e.g., code) for enabling a particular, discretefunctionality (e.g., a single task, a couple of tasks, etc.) that can beperformed by a user computing device without the user needing todownload the entire application. Such a part of an application, whichcan be called an “instant application,” can be downloaded to and openedquickly on a user computing device, even when it is not already on theuser computing device. That is, such an instant application can providemeans for running application code “on demand” on a user computingdevice and can act as a representation of a full application—native orweb—before the user commits to downloading the full application. In someexamples, data input to an instant application (e.g., via a userinterface associated therewith) can persist so that such data can beintegrated into the full application when the remaining part(s) of theapplication are downloaded onto the user computing device. In someexamples, data input to an instant application can be used to customizeand/or personalize the application, other part(s) of the application orother application(s) to surface, and/or data presented via userinterface(s) associated therewith. In one example, an instantapplication is a portion of a full application, and as such, the instantapplication can have a set of functionalities smaller than the set offunctionalities in the full application. An instant application, orapplication, can be “surfaced” on a user computing device by beingdownloaded on, or otherwise provided to, the user computing device. Auser interface associated with the instant application, or application,can be presented based at least in part on the instant application, orapplication, having been surfaced on the user computing device.

Instant applications can be discoverable. In some examples, users canuse a computing device (e.g., a user computing device) to scan, read, orotherwise interact with an interactable element associated with aparticular application (or a portion thereof). Such an interactableelement can be a Quick Response (QR) code, a radio-frequencyidentification (RFID) tag, a barcode, a near-field communication (NFC)tag, a uniform resource identifier (URI), an image, etc. In someexamples, interactable elements, which can be associated withidentification codes, can be affixed to, or otherwise associated with,physical objects, such as tables, designated seating areas, paper orelectronic receipts, bicycles, scooters, vehicles, doors, items offeredfor sale, etc. In some examples, an interactable element can bepresented via an electronic device (e.g., a buyer-facing display of apoint-of-sale device, a user computing device, a kiosk, etc.).

As described above, a user can cause an interaction between a usercomputing device and an interactable element. In some examples, a sensorassociated with the user computing device can scan, read, or otherwiseinteract with an interactable element to obtain data embedded in, orotherwise associated with, the interactable element. In some examples,the sensor can be a reader device capable of reading encoded dataassociated with RFID tags, NFC tags, or the like. In some examples,interaction with an interactable element can cause an instantapplication to be surfaced, activated, or otherwise availed on a usercomputing device. In some examples, a user can tap their user computingdevice to a card reader or another NFC device to cause an instantapplication to be surfaced, activated, or otherwise availed on the usercomputing device. In some examples, an instant application can bediscoverable via a banner associated with a web page, a link in amessage, a map user interface, a library of recently used instantapplications, a segment of a full application, or the like. In someexamples, instant applications can be discoverable based at least inpart on a geolocation of a user computing device, a time, a date, anevent, or any other context.

In at least one example, interaction with an interactable element candirect to an application server hosting a corresponding application(e.g., available via application stores for download on the computingdevice) and/or instant application(s) associated with the correspondingapplication (e.g., one or more pages, one or more functions, etc.). Insuch an example, the corresponding application and/or instantapplication(s) can be downloaded or otherwise surfaced via a usercomputing device. That is, upon discovery, a part of an application(e.g., an instant application) can be downloaded onto, and thereforeexecutable by, a user computing device and a user interface can bepresented to enable a user to interact with the portion of theapplication executable by the user computing device. An instantapplication can be discoverable “on-demand,” at a time when or alocation where users can use it, and can be focused on a specific task(e.g., booking, ordering, paying, etc.). Non-limiting examples of howinstant applications can be useful include ordering take-out from arestaurant (without downloading the full application associated with therestaurant or the take-out service provider), renting a scooter (withoutdownloading the full application associated with the scooter serviceprovider), setting up a new connected appliance (without downloading thefull application associated with the appliance service provider), payingfor parking (without downloading the full parking application), or thelike. In some examples, users can start and finish an experience inseconds, minutes, or other periods of time, and at a later time, userscan be presented with the opportunity to download the full application(or additional portions thereof). In some examples, the full applicationmay have been previously downloaded but the user needs only to access aportion thereof to perform a task. As such, a part of anapplication—instead of the full application—can be executed to performthe task, which can conserve computing resources on the user computingdevice. Additional details are provided below.

In at least one example, a user can interact with instant applicationswithout downloading corresponding applications. In some examples, if auser launches an instant application (even without downloading the fullapplication), the instant application can store data from previous usesor sessions and can leverage intelligence to learn about the user and/ortheir interactions with the instant application. Such intelligence canbe used to present recommendations, expedite an ordering process,expedite a checkout flow, customize an application, an instantapplication, and/or data presented via a user interface associated withthe application and/or instant application, and/or the like. In someexamples, if a user decides to download the full instant application,data previously provided to the instant application can be used by thefull application to streamline the handoff. In some examples,authorization provided for access to a camera, a microphone, Bluetooth,etc., which has already been requested by the instant application, canbe provided to the full application to further streamline the handoff.In another example, data input via the instant application can be storedand transferred to the full application when downloaded. Such data canbe used for customization and/or personalization and can expediteprocesses associated with the full application. As an example, if aportion of onboarding is completed via an instant application, thestorage and transfer of data associated with the portion of onboardingcompleted can expedite onboarding via the full application. The userneed not re-enter data previously provided and thus can accessfunctionality associated with the full application faster and with fewerinteractions with a user interface of the full application.

In some examples, a service provider can be associated with multipleinstant applications. As an example, a service provider can havemultiple instant applications to support multiple selling verticalsand/or horizontals including, but not limited to, restaurants, retailstores, appointments, peer-to-peer payments, etc. Techniques describedherein can intelligently determine which instant application(s) tosurface to a user computing device and/or when to surface such instantapplication(s) based at least in part on context data. In some examples,such intelligence can be provided by one or more models, trained viamachine learning mechanisms, based at least in part on data previouslyreceived by a service provider. Such data can be received in associationwith one or more interactions and/or transactions between users ofservice(s) of the service provider. Additional details are providedbelow.

In at least one example, a service provider can offer multiple differentapplications for use by merchants, and each application can have one ormore parts that can be accessible via an instant application. Examplesof merchant-facing applications can include a point-of-sale applicationfor managing point-of-sale interactions, an ecommerce application formanaging online interactions, an employer application for workermanagement (e.g., management of employees, independent contractors,agents, and/or the like), a payroll application for managing payroll, anappointments application for managing appointments, an inventoryapplication for managing inventory, and/or the like. Additional oralternative applications can be available for one or more of theservices availed by the service provider, as described below. In someexamples, individual merchants can customize aspects of applicationsused by the merchants.

Further, in some examples, the service provider can have one or moreapplications for use by buyers, and each application can have one ormore parts that can be accessible as an instant application. An exampleof a buyer-facing application can include an application that enablesbuyers to browse inventory, place orders, track fulfillment, makepayments, and/or the like. Other examples of applications associatedwith a service provider, that can be associated with one or more parts,can be a peer-to-peer payment application, a mobile payment application,a wallet application, or the like. Such applications can be used bybuyers or non-buyers.

Techniques described herein can intelligently and dynamically determinewhich instant application(s), or which combination or sequence ofinstant application(s), to present for a specific context (e.g., aparticular user, date, time, location, etc.). In at least one example,such “on-demand” determinations can be based, at least in part, oncontext data. For instance, techniques described herein can utilizecontext data to determine which instant application to cause to bedownloaded, or otherwise surfaced, on a user computing device responsiveto receiving an indication of an interactable element that is mapped toor otherwise associated with multiple instant applications (e.g., amulti-function interactable element). In an additional or alternativeexample, techniques described herein can utilize context data todetermine which instant application to recommend or otherwise present toa user (which, in some examples can implement dynamic interactableelements). That is, techniques described herein are directed todynamically and/or intelligently determining which instant applicationsto avail to users—and, in some examples, when—based at least in part oncontext data. Additional details are described below.

Techniques described herein can use machine learning to determine whichinstant applications to surface, thus allowing a string of unrelatedinstant applications (server-specific or merchant-specific) to beconnected by trigger actions. Some merchants may be using a singlepayment processing system, credit management system, lending system,etc., and those systems can leverage associated data to stitchunaffiliated merchants, and their instant applications, together. Asdescribed below, techniques described herein can be implemented in amulti-party, networked ecosystem, wherein a service provider can provideapplications (or parts thereof) to specially configure end-usercomputing devices to perform operations as described herein. In someexamples, multiple, different merchants, buyers, and/or other users canutilize the service provider for different services, as described below.Instant applications, as described herein, can be associated with partsof applications offered by the service provider and/or users utilizingservices availed thereby. With a centralized, remote location, theserver(s) can have access to applications and/or instant applicationsassociated with its own services and/or applications and/or instantapplications associated with merchants, for example, using services ofthe service provider. Accordingly, by leveraging the multi-party,networked ecosystem, the server(s) can dynamically determine whichinstant application(s) to surface to individual users based on contextdata, as described herein. The server(s) can do so, with morepersonalization and/or customization, and, in some examples, with moreaccuracy and/or precision, than existing technologies. That is,techniques described herein can leverage the multi-party, networkedecosystem to dynamically determine which instant application(s) tosurface to user(s) and, in some examples, when to surface such instantapplication(s), with more efficiency and personalization and/orcustomization than existing technologies.

In some examples, an instant application can leverage an existing, butunrelated, full application to offer some of the functionalitiesassociated with the instant application. In such examples, the instantapplication can rely on a previously downloaded full application toprovide a limited set of functionalities within the full applicationwithout needing to download another full application corresponding tothe instant application. Accordingly, techniques described herein relateto a more resource-efficient way to re-use and/or share memory allocatedto one application.

Instant applications can offer improvements to existing computingtechnologies. For instance, instant applications can enable users todownload and utilize a portion of an application (i.e., a small amountof code) that can be downloaded quickly without having to download theentire application, which can be associated with more code and thereforelonger and more computationally intensive downloads. Not only caninstant applications enable users to consume less data (and thus lessnetwork resources), instant applications can further enable a reductionin storage resources associated with storing applications that are notused and/or a majority of which are not used. As described above,applications can require a significant amount of memory and can be usedso infrequently that downloading the entire application can be a wasteof computing resources. Thus, techniques described herein can be usefulfor conserving storage resources in addition to conserving networkresources.

Instant applications can be merchant-facing, buyer-facing, or both. Insome example, the same instant application can present different data tothe buyer and merchant, depending on context data, for example, for thesame transaction. That is, techniques described herein can utilizecontext data to dynamically offer one or more instant applications todifferent users based on their individual contexts. In some examples,the same instant application(s) can be presented in the same order todifferent users. In some examples, the same instant application(s) canbe presented in different orders to different users. In some examples,different instant application(s) can be presented in the same ordifferent orders to different users. In some examples, data presentedvia instant applications can be the same or different, dependent on usercontext.

In some implementations, an application programming interface (API) canbe used to automate adding/removing/modifying instant applications froma user computing device and determining which user data persists andwhich does not. In some examples, APIs can be used to embed or otherwiseintegrate third-party applications, or parts thereof, into nativeapplications, or parts thereof. Examples are provided below.

While techniques described herein describe a small amount (e.g., lessthan LOMB) of data to surface an instant application, it can beunderstood that examples described herein can be implemented usingprogressive web applications (PWAs). Additionally or alternatively,techniques described herein can also be applied with technologies thatallow viewing of data without any download on a local device. Further,these technologies can also be applied to generate a “shell” of the fullapplication, which can be a condensed version of the full application,made to look and feel like a full application. Moreover, in someexamples, techniques described herein can be applicable to fullapplications.

FIG. 1 illustrates an example environment 100 for performing techniquesdescribed herein. The example environment 100 includes server(s)associated with a service provider (i.e., “service provider server(s)”102) and at least one user computing device 104, which can be operableby a user 106. While only a single user computing device 104 and user106 are illustrated, the environment can have tens, hundreds, thousands,millions, etc. of user computing devices and users in practice. Theservice provider server(s) 102 can communicate with the user computingdevice 104 and/or server(s) associated with third-party(s) (i.e.,“third-party server(s)” 108) via network(s) 110. Additional detailsassociated with the user computing device 104 and/or the server(s)(e.g., the service provider server(s) 102 and/or the third-partyserver(s) 108) are described below.

In at least one example, the service provider server(s) 102 can have oneor more functional components for providing operations described herein.As illustrated, the service provider server(s) 102 can optionallyinclude a merchant component 112, a buyer component 113, an applicationmanagement component 114, a context determination component 116, and oneor more data stores 118. In at least one example, operations attributedto the “service provider” can be performed by one or more of thefunctional components associated with the service provider server(s)102.

In at least one example, the merchant component 112 can be configured toreceive transaction data from point-of-sale (POS) systems and/orecommerce systems as described herein. That is, the merchant component112 can enable the service provider to provide, among other services,payment processing services on behalf of a plurality of differentmerchants. The service provider can be an intermediary or aggregatorthat can receive transaction data associated with transactions betweenbuyers and merchants and can utilize payment data associated with thetransaction data to process payments for the transactions. For example,the merchant component 112 can transmit requests (e.g., authorization,capture, settlement, etc.) to payment service server computing device(s)to process payments for the transactions. Additional details areprovided below.

In at least one example, the buyer component 113 can be configured tocommunicate with buyer application(s) as described herein. In at leastone example, a buyer application can be a peer-to-peer paymentapplication and the buyer component 113 can facilitate peer-to-peerpayments between users associated with the service provider. In at leastone example, the service provider can provide a peer-to-peer paymentservice that enables peer-to-peer payments between two or more users(e.g., the user 106 and another user). In at least one example, thebuyer component 113 can communicate with an instance of the peer-to-peerpayment application (or other access point) installed on the usercomputing device 104. In an example, the user 106 can be a payor, and aninstance of the peer-to-peer payment application executing on the usercomputing device 104 can send a request to the buyer component 113 totransfer an amount of funds (e.g., fiat currency or non-fiat currencysuch as cryptocurrency, securities, and related assets) from an accountof the payor to an account of a payee (e.g., a peer-to-peer payment).The buyer component 113 can facilitate the transfer and can send anotification to an instance of the payment application executing onanother user computing device operated by the payee that the transfer isin process (or has been completed). In an example where the user 106 isa payee, the user computing device 104 can receive such a notificationand can cause the notification to be presented via the user computingdevice 104. In some examples, the buyer component 113 can sendadditional or alternative data to the instance of the peer-to-peerpayment application (e.g., low balance to the payor, current balance tothe payor or the payee, etc.). Additional details are provided below. Inexamples where the buyer application is another application, the buyercomponent 113 can be configured to facilitate operations associatedtherewith.

In at least one example, the application management component 114 cangenerate interactable elements associated with one or more applicationsand/or part(s) associated therewith (e.g., instant application(s)associated therewith). The parts may include a subset (or all) of thepages and/or functionality of the overall application. Examples ofinteractable elements are described throughout.

In at least one example, an interactable element can be directed to oneor more applications, which can include, but are not limited to, instantapplications or PWAs. As described above, an instant application cancomprise a part of a full application. In at least one example, aninstant application is a non-persistent application that may bedynamically downloaded and installed on a user computing device 104.Furthermore, instant applications correspond to a subset of anapplication that can be chosen based on a particular function to beperformed, while the remainder of the application can be downloadedlater (or as part of a background process). For example, the instantapplication may be a subset of a merchant POS application that performsa variety of functions, while the instant application can comprise oneor more parts of merchant POS application and/or a subset of functionsprovided by the POS application, e.g., payments functionality orinventory functionality. A PWA can be an application, or part thereof,that can be built using web technologies (e.g., HTML, CSS, JavaScript)and can be delivered through a web browser. PWAs can be on-demandapplications that execute in a web browser and remain persistent whenexecuting on a user computing device 104. For example, a PWA can beallocated storage of a user computing device 104 and can be updated inthe background when new functionality is added to the PWA. A PWA cancorrespond to a subset of an application that is chosen based on aparticular function to be performed.

In at least one example, the application management component 114 canutilize context data associated with the user computing device 104 toselect applications and/or part(s) associated therewith (e.g., instantapplication(s)) to surface to the user computing device 104. In someexamples, the application management component 114 can determining atiming associated with surfacing of application(s) and/or part(s)associated therewith and/or a sequence (e.g., order) associated withsurfacing a plurality of applications or part(s) associated therewith.In some examples, the application management component 114 can accessdata associated with the user 106 and/or the user computing device 104to customize and/or personalize an application, a part associatedtherewith (e.g., an instant application), and/or data presented via auser interface associated with the application and/or the instantapplication. In some examples, the application management component 114can receive a request to download an application (e.g., via anassociated instant application) and can facilitate such a download.Additional details are provided below.

In at least one example, the context determination component 116 candetermine and/or receive context data associated with user computingdevice(s), such as the user computing device 104. In at least oneexample, context data can include location data indicating a location ofthe user computing device 104. In some examples, the context data caninclude interaction data indicating whether the user 106 is interactingwith the user computing device 104, an application with which the user106 is interacting, and/or the like. In some examples, context data beassociated with time data (e.g., timestamps, etc.), date data (e.g.,datestamps, etc.), event data (e.g., data indicating details associatedwith events), calendar data (e.g., data associated with an electroniccalendar, holidays, etc.), activity data (e.g., data associated withpast transactions and/or interactions of a user, etc.), transaction data(e.g., data associated with previous, current, and/or futuretransactions), user data, device data (e.g., version of softwareexecuting on the user device 104, network configuration, etc.) and/orthe like. In some examples, at least a portion of the context data canbe accessed and/or received from the data store(s) 118.

The data store(s) 118 can manage and/or store data. In at least oneexample, the data store(s) 118 can include application(s) 120 and userdata 122. The application(s) 120 can comprise one or more applicationsprovided by the service provider (e.g., developed and/or managed by theservice provider). The application(s) 120 can comprise one or moreapplications provided by one or more third parties (e.g., developedand/or managed by an entity other than the service provider). In atleast one example, an application 124 of the application(s) 120 cancomprise multiple parts. As described above, parts of applications canbe executed on user computing device(s) quickly and without user(s)needing to download the entire application onto the user computingdevice(s). That is, in an example, a part of an application can includeinstructions (e.g., code) for enabling a particular, discretefunctionality (e.g., a single task, a couple of tasks, etc.) that can beperformed by the user computing device 104 without the user 106 needingto download the entire application. Each part, such as the part 126, canbe associated with an instant application and can be downloaded to andopened quickly on the user computing device 104, even when it is notalready on the user computing device 104. That is, such an instantapplication can provide means for running application code “on demand”on the user computing device 104 and can act as a representation of afull application—native or web—before the user commits to downloadingthe full application.

In some examples, the application(s) 120 and/or instant applicationsassociated therewith can be customizable such that users can designatecontext for when particular instant applications should be presented,what functionality(s) are available via an instant application, in whichorder (if applicable), and the like. In some examples, someapplication(s) can be stored and/or accessible via the third-partyserver(s) 108. In examples where one or more applications are stored inthird-party server(s) 108, the third-party server(s) 108 can ping theservice provider server(s) 102 when the user starts to interact with anapplication associated with the third-party server(s) 108. Thethird-party server(s) 108 and the service provider server(s) 102 cantransmit data to facilitate operations as described herein.

As described above, the data store(s) 118 can provide a specificpartition of the memory or memory address to be used in one or more ofthe server(s) for the application(s) 120. This allows the data store(s)118 to overlap instant applications and prevent instant application(s)associated with a single server from taking too many memory and networkresources. In some examples, however, the data store(s) 118 can allow aplurality of applications to be on a server computing device dependingon whether the instant applications will be used contemporaneously orare otherwise dependent on each other.

The user data 122 can comprise user data associated with one or moreusers of services availed via the service provider. In some examples,the user data 122 can include merchant profiles and buyer profiles.

Merchant profiles can store, or otherwise be associated with, dataassociated with merchants. For instance, a merchant profile can store,or otherwise be associated with, data about a merchant (e.g., name ofthe merchant, geographic location of the merchant, operating hours ofthe merchant, worker data, etc.), a merchant category classification(MCC), item(s) offered for sale by the merchant, hardware (e.g., devicetype) used by the merchant, transaction data associated with themerchant (e.g., transactions conducted by the merchant, payment dataassociated with the transactions, items associated with thetransactions, descriptions of items associated with the transactions,itemized and/or total spends of each of the transactions, parties to thetransactions, dates, times, and/or locations associated with thetransactions, etc.), loan data associated with the merchant (e.g.,previous loans made to the merchant, previous defaults on said loans,etc.), risk data associated with the merchant (e.g., indications ofrisk, instances of fraud, chargebacks, etc.), appointments data (e.g.,previous appointments, upcoming (scheduled) appointments, timing ofappointments, lengths of appointments, etc.), payroll data (e.g.,workers, payroll frequency, payroll amounts, etc.), worker data,reservations data (e.g., previous reservations, upcoming (scheduled)reservations, interactions associated with such reservations, etc.),inventory data, buyer service data, etc. The merchant profile cansecurely store bank account data as provided by the merchant.

Buyer profiles can store buyer data including, but not limited to, buyerdata (e.g., name, phone number, address, banking data, etc.), buyerpreferences (e.g., learned or buyer-specified), purchase history data(e.g., identifying one or more items purchased (and respective itemdata), payment instruments used to purchase one or more items, returnsassociated with one or more orders, statuses of one or more orders(e.g., preparing, packaging, in transit, delivered, etc.), etc.),appointments data (e.g., previous appointments, upcoming (scheduled)appointments, timing of appointments, lengths of appointments, etc.),payroll data (e.g., employers, payroll frequency, payroll amounts,etc.), reservations data (e.g., previous reservations, upcoming(scheduled) reservations, reservation duration, interactions associatedwith such reservations, etc.), inventory data, buyer service data, etc.

In some examples, the user data 122 can be associated with user profilesof other users of the service provider, such as users of peer-to-peerpayment services. In such examples, a user profile can store user dataincluding, but not limited to, user data (e.g., name, phone number,address, banking data, etc.), user preferences (e.g., learned oruser-specified), purchase history data (e.g., identifying one or moreitems purchased (and respective item data), payment instruments used topurchase one or more items, returns associated with one or more orders,statuses of one or more orders (e.g., preparing, packaging, in transit,delivered, etc.), etc.), peer-to-peer activity data (e.g., payments madeto other users, payments received from other users, etc.), appointmentsdata (e.g., previous appointments, upcoming (scheduled) appointments,timing of appointments, lengths of appointments, etc.), payroll data(e.g., employers, payroll frequency, payroll amounts, etc.),reservations data (e.g., previous reservations, upcoming (scheduled)reservations, reservation duration, interactions associated with suchreservations, etc.), inventory data, user service data, etc.

The user computing device 104 can present a user interface 128, whichcan be provided by a web browser, application, instant application, orthe like. In some examples, content presented via the user interface 128can be customized and/or personalized based at least in part on contextdata and/or data received via input(s) to the user interface 128.Additional details associated with the user interface 128 and/or webbrowser(s), application(s), instant application(s), or the like that canpresent the user interface 128 are provided below. That is, any of theuser interfaces described below can correspond to the user interface128, which can enable the user 106 to interact with the associated webbrowser, application, instant application, or the like.

While techniques described below are described with reference to instantapplications (i.e., parts of full applications), in some examples,techniques can be applicable to full applications in addition to, or asan alternative of, instant applications. That is, to the extentselection of an instant application is described, in some examples, sameor similar techniques can be used for selecting an application insteadof an instant application.

FIG. 2 illustrates an example process 200 for selecting an instantapplication based at least in part on context data associated with auser computing device and causing a user interface associated with theselected instant application to be surfaced via the user computingdevice.

At operation 202, application(s) 120 can be stored in a repository(e.g., the data store(s) 118) associated with a service provider. Asdescribed above, the data store(s) 118 can manage and/or store data. Inat least one example, the data store(s) 118 can include application(s)120 and user data 122. The application(s) 120 can comprise one or moreapplications provided by the service provider (e.g., developed and/ormanaged by the service provider). The application(s) 120 can compriseone or more applications provided by one or more third parties (e.g.,developed and/or managed by an entity other than the service provider).In at least one example, an application 124 of the application(s) 120can comprise multiple parts. Each part, such as the part 126, can beassociated with an instant application, as described above, which canprovide a particular, discrete functionality when downloaded.

At operation 204, the context determination component 116 can determinecontext data associated with a user computing device 104. In at leastone example, the context determination component 116 can determineand/or receive context data associated with user computing device(s),such as the user computing device 104. In at least one example, contextdata can include location data indicating a location of the usercomputing device 104. In some examples, the context data can includeinteraction data indicating whether the user 106 is interacting with theuser computing device 104, an application with which the user 106 isinteracting, and/or the like. In some examples, context data beassociated with time data (e.g., timestamps, etc.), date data (e.g.,datestamps, etc.), event data (e.g., data indicating details associatedwith events), calendar data (e.g., data associated with an electroniccalendar, holidays, etc.), activity data (e.g., data associated withpast transactions and/or interactions of a user, etc.), transaction data(e.g., data associated with previous, current, and/or futuretransactions), user data, and/or the like. In some examples, at least aportion of the context data can be accessed and/or received from thedata store(s) 118.

In at least one example, the context determination component 116 candetermine context data which can include, but is not limited to, alocation of the user computing device 104, a date, a time, a currentbehavior of one or more friends of the user, a preference of the user,an occurrence of an event, and/or the like.

In at least one example, context data can be associated with a locationof the user computing device 104. The location of a user computingdevice 104 can be determined using one or more techniques. For example,the location of a user computing device 104 can be determined based atleast in part on an interaction with another computing device associatedwith a known location (e.g., a merchant computing device associated witha particular location). In some examples, the location of the usercomputing device 104 can be determined based at least in part ondetermining that the user computing device 104 is within a thresholddistance of another computing device associated with a known location(e.g., a merchant computing device associated with a particularlocation). In at least one example, a location of the user computingdevice 104 can be determined, based at least in part on Bluetooth/BLEbeacons associated with another computing device associated with a knownlocation (e.g., a merchant computing device associated with a particularlocation). For example, if the user computing device 104 is determinedto be within a threshold distance of a computing device of a merchant,the context determination component 116 can determine that the locationof the user of the computing device 104 corresponds to the merchant.

In at least one example, location data (e.g., GPS data) received fromthe user computing device 104 can be used to determine the location ofthe user computing device 104. In some examples, signal strength can beused to determine the location of the user computing device 104. Forinstance, the location of the user computing device 104 can bedetermined based at least in part on determining how the user computingdevice 104 responds to a signal emitted by another computing deviceassociated with a known location (e.g., a merchant computing deviceassociated with a particular location). Moreover, in at least oneexample, the location of the user computing device 104 can be determinedbased at least in part on determining that the user computing device 104has joined a same network as another computing device associated with aknown location (e.g., a merchant computing device associated with aparticular location).

In at least one example, a time and/or date can be determined based atleast in part on time or date data associated with the user computingdevice 104 and/or the service provider server(s) 102.

In at least one example, at least a portion of the user data 122 (e.g.,buyer data, merchant data, etc.) can be used to determine context data.For example, based at least in part on receiving an identifierassociated with a user (e.g., a device identifier or other device dataassociated with the user computing device 104, an email, a user name, aphone number, a cookie, a token, etc.), the context determinationcomponent 116 can access data associated with the user, which in someexamples, can be stored in profile(s) stored in the data store(s) 118.Additional details associated with such profile(s) and/or associateddata are described below. Such user data can be used to identify userpreferences of the user, friends of the user, behaviors of the user(and/or friends of the user), and the like. Additional or alternativethird-party data sources can also be accessed, e.g., via APIs, to refinecontext. For example, such sources can provide data such as restaurantmenus, merchant MCCs, etc.

In some examples, the context determination component 116 can determinean occurrence of an event, such as an order, payment, or the like, andcan determine context data based at least in part on the occurrence ofthe event. That is, the occurrence of an event can be used to determinecontext data. In some examples, events can be determined based at leastin part on interaction data representative of interactions betweenbuyers and merchants and/or other users associated with the serviceprovider. Such interaction data can include transaction data, which canbe used for processing payments for transactions, order data, payrolldata, appointment data, lending data, or the like.

In some examples, the context determination component 116 can determinecontext data based at least in part on device data, which can includedevice attributes, of the user computing device 104. For example, thedevice attributes may be used to determine which functionality topresent. Other example attributes describing the user computing device104 can include detected versions of software installed in the operatingsystem of the user computing device 104, the speed of a networkconnection of the user computing device 104, remaining battery life ofthe user computing device 104, etc. So, for example, if the usercomputing device 104 has a slow network connection and/or littleremaining battery life, the applications, or parts thereof, selected maybe the ones with the appropriate size that can perform the requiredfunctions.

At operation 206, the application management component 114 can select,based at least in part on the context data, an instant applicationassociated with one of the application(s) 120. In at least one example,the application management component 114 can utilize context dataassociated with the user computing device 104 to select applicationsand/or part(s) associated therewith (e.g., instant application(s)) tosurface to the user computing device 104. That is, in at least oneexample, the application management component 114 can determine whichinstant application to surface to the user computing device 104 based atleast in part on the context data.

In at least one example, the application management component 114 cananalyze the context data using a machine-trained model, such that themodel can be trained with context data of one or more users (e.g., userssimilar to the user, users of a cohort, all users associated with theservice provider, etc.), as an example. The machine-trained model canoutput one or more recommended instant applications to provide to theuser computing device 104 based at least in part on the context dataassociated with the user computing device 104. In some examples,individual of the recommended instant applications can be associatedwith relevance scores, or other metrics, indicating a relevance to theuser in view of the context data. In some examples, the recommendedinstant applications can be ranked based at least in part on therelevance scores. In some examples, the application management component114 can select a highest-ranking recommended instant application, aninstant application with a relevance score above a threshold, or thelike.

In at least one example, the application management component 114 cangenerate interactable elements associated with one or more applicationsand/or part(s) associated therewith (e.g., instant application(s)associated therewith). In some examples, an interactable element can bemapped one-to-one to an instant application. In such examples, theapplication management component 114 can select the instant applicationmapped to the interactable element based at least in part on receivingthe indication of the interaction with the interactable element. In someexamples, an interactable element can be mapped to multiple instantapplications (e.g., one-to-many) as a multi-functional interactableelement. In such examples, the application management component 114receive an indication of an interaction with the multi-functionalinteractable element and can analyze the context data to select aninstant application of the multiple instant applications associated withthe multi-functional interactable element to recommend for surfacing onthe user computing device 104. In some examples, the applicationmanagement component 114 can use statistics, machine-learning, or othertechniques to select an instant application. In some examples, theapplication management component 114 can use context data to determinerisk associated with the user. Such risk can also factor intodetermining which of the instant applications the user qualifies for,and thus, which instant application(s) to present to the user.

In some examples, the application management component 114 can receivecontext data over a period of time. In such examples, the applicationmanagement component 114 can determine changes and/or otherwise trackthe user 106 and/or user computing device 104 over the period of time.In some examples, the application management component 114 can select aninstant application based at least in part on such changes and/ortracking. As an example, the application management component 114 canreceive location data over a period of time. Using the location data,the application management component 114 can track the user computingdevice 104 and can select the instant application based at least in parton such tracking. That is, if the user computing device 104 is movingtoward a particular entity associated with an instant application (e.g.,a bicycle, a food truck, a merchant, etc.), the application managementcomponent 114 can select an instant application associated with theentity. As a non-limiting example, if the user computing device 104 ismoving toward a restaurant, the application management component 114 canselect an instant application associated with the restaurant to enablethe user 106 to add their name to a wait list, make a reservation, placean order, or the like.

At operation 208, the application management component 114 can cause auser interface 128 associated with the instant application to bepresented via the user computing device 104. In at least one example,the application management component 114 can send instructions and/orcode related to the selected instant application over the network(s) 110to enable the user computing device 104 to provisionally or temporarilydownload the instant application. Functionality associated with theinstant application can be made available “on demand” or in near-realtime. As such, the user can quickly access the functionality, withouthaving to download the entire application.

In some examples, the instant application can be downloaded upondetermining such a recommendation (e.g., based on an implied or explicitconsent from the user). In some examples, a recommendation or othernotification associated with an instant application can be presented viathe user interface 128 of the user computing device 104 and/or anothercomputing device (from which an interactable element can be presented).In some examples, the recommendation can include an interactable elementor other mechanism for the user 106 to provide an input to initiate thedownload of the instant application. In such examples, the user 106 canprovide an input indicating consent for the instant application to bedownloaded on the user computing device 104. In some examples, such aninput can comprise interacting with the interactable element (e.g.,scanning or otherwise reading the interactable element), which can beprovided to the service provider server(s) 102 and the applicationmanagement component 114 can thereby cause the instant application to bedownloaded on the user computing device 104 based at least in part onreceiving the indication of the interaction with the interactableelement.

In at least one example, based at least in part on receiving theinstructions and/or code, the user computing device 104 can cause theuser interface 128 to be presented via the user computing device 104. Insome examples, content presented via the user interface 128 can becustomized and/or personalized based at least in part on the contextdata. In at least one example, the user interface 128 enables the user106 of the user computing device 104 to input data for enabling theparticular, discrete functionality. Non-limiting examples of such a userinterface are provided below. In at least one example, the instantapplication can present the user interface 128 to enable the user 106 toinput data into the application. In some examples, such data can be aname and password. In some examples, such data can be payment data. Insome examples, such data can be an address (e.g., for delivery). In someexamples, the user interface 128 can enable a user to perform anoperation such as ordering an item, purchasing an item, redeemingloyalty points or rewards, or the like. Additional examples of dataand/or input that can be provided via the user interface presented bythe instant application are described below.

In some examples, each session with the instant application can be timedsuch that the instant application is removed from the user computingdevice 104 when the session is over. In some examples, the applicationmanagement component 114 can track and cache/store such session activitywith identifiers (e.g., user name, device identifier (ID), merchantidentifier (ID), merchant card reader identifier, etc.) and cansurface/prepopulate part or some of the tracked data to the user 106 viathe user interface 128 when a subsequent session starts with the instantapplication initialization. In some cases, the tracked data (e.g.,session data) can also be used (e.g., as context data) to automaticallyrecommend an instant application based on known historical sessionactivity of the same user and/or similar users when a predefinedcondition is met (e.g., the user is at the same merchant location). Inat least one example, users can be determined to be “similar” based atleast in part on comparing data associated with such users. In someexamples, such data can be obtained from profile(s) associated with suchusers that can be stored in a data store associated with the serviceprovider server(s) 102. In at least one example, similarity algorithms(e.g., nearest neighbor, regression similarity, classificationsimilarity, ranking similarity, etc.) can be used by the server(s) todetermine similarity between users.

In some examples, the instant application can send an authorizationrequest to the service provider server(s) 102 to request access to datastored by the service provider server(s) 102 (e.g., in the data store(s)118). The application management component 114 can receive the requestand can determine whether to authorize access to at least a portion ofthe data stored by the service provider server(s) 102. In some examples,the portion of data can be associated with the user 106 and/or the usercomputing device 104 and can be used for customizing and/orpersonalizing at least one of the instant application, data presentedvia a user interface associated with the instant application, and/or thefull application with which the instant application is associated.

At operation 210, the application management component 114 can determinewhether a request to download the application is received. In someexamples, remaining part(s) of the application can be downloaded at alater time. That is, the full application can be downloaded at a latertime. In some examples, a recommendation or notification can bepresented via the instant application that can prompt the user 106 todownload one or more remaining parts of the application to the usercomputing device 104. If a request to download the application isreceived, the application management component 114 can facilitatedownloading of the application onto the user computing device 104, asillustrated at operation 212.

In some examples, prior to facilitating the downloading of theapplication onto the user computing device 104, the applicationmanagement component 114 can access user data associated with the user106 and can customize and/or personalize at least one of the applicationor data presented via the application based at least in part on the userdata. In some examples, the application management component 114 canutilize input received via the instant application to access the userdata. For instance, in some examples, the user 106 can input a nameand/or password, a physical address, an email address, payment data, orthe like, which can be used by the application management component 114to access the user data (e.g., from the data store(s) 118). In someexamples, the application management component 114 can use an additionalor alternative identifier, such as an identifier associated with theuser computing device 104 or the like to access the user data.

In some examples, as described above, data input to an instantapplication can persist so that such data can be integrated into thefull application when the remaining part(s) of the application aredownloaded onto the user computing device 104. In such examples, basedat least in part on receiving a request to download the application, theapplication management component 114 can store data provided via theinstant application. The application management component 114 canassociate the data provided via the instant application with theapplication such that the data can be accessible via the applicationafter the application has been downloaded on the user computing device104. In some examples, data input to an instant application can be usedto customize and/or personalize the application, other part(s) of theapplication to surface, and/or data presented via user interface(s)associated therewith.

In at least one example, if the user decides to move from an instantapplication to a full application, the application management component114 can provide data and context, for example, data obtained from otherof the application(s) 120, other contextual data from similar users, inaddition to session data obtained by the user computing device 104during the use of the instant application, through server calls toimprove the onboarding and integration experience. In such an example,the service provider server(s) 102 can offer intelligence related to theuser's transaction and activity history to better configure the instantapplication or the full application. That is, context data can be usedto personalize or customize an instant application or a fullapplication, or in some examples, data presented via user interface(s)associated therewith.

In an example, consider a user downloads an instant application to payfor a bike rental on their user computing device. In such an example,the instant application allows the user to perform two tasks—rent thebike (physically unlock the bike as an authorized user after payment isconfirmed) and pay for the bike rental (enter credit card data on apayment interface within the instant application or through a nativepayment application). In response to data obtained from the bike rentaltransaction (e.g., credit card data and/or user identifier), theapplication management component 114 can determine whether the user orthis transaction data matches any other user associated with the serviceprovider, for example using user transaction history, user peer-to-peerpayment history, or the like. If the user or a user matching, orotherwise determined to be similar to, the user's profile is detected,the application management component 114 can package and encrypt dataand send to the instant application to apply to this user session or asubsequent user session. Alternatively or additionally, the applicationmanagement component 114 can package and apply this data (for examplefor risk determination) to configure/transport to a full application ata later time. The application management component 114 can also querythe data store(s) 118 for rich data at, or near, the time the user 106commits to moving from instant application to full application. In someexamples, the user 106 can provide a username and/or other credentialsto access third-party data sources for the purposes defined above. Thiscan allow a seamless onboarding experience with intelligence obtainedfrom other areas of the service provider server(s) 102 and/orenvironment 100 described above.

In some examples, if a request to download the application is notreceived, the application management component 114 can send anindication of an incentive to the user computing device 104, asillustrated at operation 214. In at least one example, the incentive canprovide a benefit to the user 106 based at least in part on adetermination that one or more conditions associated with the incentiveare satisfied. In at least one example, a condition associated with theincentive can require that the application to which the instantapplication corresponds be downloaded onto the user computing device104. In at least one example, the indication of the incentive can bepresented via the user interface 128. In at least one example, theapplication management component 114 can determine whether a request todownload the application is received (i.e., responsive to theincentive), as illustrated at operation 216. If a request to downloadthe application is received, the application management component 114can facilitate downloading of the application onto the user computingdevice 104, as illustrated at operation 212. In such an example, basedat least in part on a determination that condition(s) associated withthe incentive have been satisfied (e.g., one or more remaining part(s)of the application have been downloaded) the application managementcomponent 114 can provide the incentive to the user 106. That is, theapplication management component 114 can associate the incentive with auser profile of the user, send the incentive via an email, text message,push notification, or the like. In some examples, the process 200 canrepeat operations 214 and 216 for a predetermined number of attempts, apredetermined period of time, or the like (e.g., as illustrated by thedashed line between operation 216 and 214).

If a request to download the application is not received, theapplication management component 114 can refrain from facilitatingdownloading of the application, as illustrated at operation 218. In someexamples, if the application has not been downloaded after thepredetermined number of attempts, the predetermined period of time, orthe like, the application management component 114 can refrain fromproviding the application to the user computing device 104 (e.g., fordownload). In some examples, a prompt to download the application can beblocked and/or hidden.

In some examples, the process 200 can proceed from operation 210directly to operation 218 if a request to download the application isnot received (i.e., the application management component 114 can refrainfrom sending an incentive), as illustrated by the dashed line betweenoperations 210 and 218.

In some examples, multiple instant applications can be available to theuser computing device 104. In some examples, two or more instantapplications can be associated with particular, discrete functionalitiesthat can be performed serially and/or in a sequence (and without theuser needing to download the full application). For example, a firstinstant application can be associated with clocking in, a second instantapplication can be associated with clocking out, and a third instantapplication can be associated with requesting a payout for compensation(e.g., gratuities earned during time work, compensation owed for timeworked, etc.). In some examples, a worker (e.g., an employee,independent contractor, agent, and/or the like) can download each of theinstant applications serially such that the worker can clock-in, andlater clock-out and request payout for compensation, in that order. Insome examples, two or more instant applications can be associated with asame application or a different application. For instance, the firstthrough third instant applications described above can each beassociated with a same employer application. In an alternative example,however, the first, the second, and/or the third instant application canbe associated with the employer application or a separate payrollapplication. In at least one example, the instant applications involvedin the sequence and/or the order of the sequence can be determined basedat least in part on context data, as described herein.

In some examples, previously downloaded instant applications can be usedas context data for selecting one or more subsequent instantapplications. As an example, based at least in part on a userdownloading a first instant application associated with a firstmerchant, the context determination component 116 can cause a secondinstant application associated with a second merchant to be downloadedon the user computing device. In at least one example, the secondinstant application can be associated with a promotion, incentive,reward, or the like to encourage the user to patronize the secondmerchant. For instance, the second instant application can offer anincentive for making an appointment with and/or purchase from the secondmerchant and can present a user interface to enable the user to make theappointment. Additional or alternative examples are provided below.

FIG. 3 illustrates an example process 300 for selecting an instantapplication based at least in part on context data associated with auser computing device and causing a user interface associated with theselected instant application to be surfaced via the user computingdevice.

At operation 302, application(s) 120 can be stored in a repository(e.g., the data store(s) 118) associated with a service provider, asdescribed above with reference to operation 202 of FIG. 2.

At operation 304, the application management component 114 can generatean interactable element associated with a part of an application of theapplication(s) 120. As described above, an interactable element, whichcan include an identification code, can comprise a QR code, a RFID tag,a barcode, an NFC tag, a URI, an image, etc. In some examples, aninteractable element can be affixed to, or otherwise associated with,physical objects, such as tables, designated seating areas, receipts,bicycles, scooters, vehicles, doors, items offered for sale, etc. Insome examples, an interactable element can be presented via a computingdevice. In at least one example, interactable element(s) associated witha part of an application (e.g., an instant application) can be mappedto, or otherwise associated with, the part of the application in thedata store(s) 118.

At operation 306, the context determination component 116 can determinecontext data associated with a user computing device 104 of a user 106,as described above with reference to operation 204 of FIG. 2.

At operation 308, the application management component 114 can select,based at least in part on the context data, an instant application tosurface via the user computing device 104, the instant application beingassociated with the part of the application. Details associated withselecting an instant application are described above with reference tooperation 206 of FIG. 2. In some examples, the application managementcomponent 114 can cause the interactable element associated with theselected instant application to be presented via the user interface 128of the user computing device 104. In some examples, the applicationmanagement component 114 can send the interactable element to the usercomputing device 104 via a text message, email, push notification, orthe like. In at least one example, the application management component114 can cause the interactable element to be presented via another usercomputing device (e.g., a buyer-facing display of a point-of-saledevice, a merchant computing device, a kiosk, etc.).

At operation 310, the application management component 114 can receive,from the user computing device 104, an indication of an interaction withthe interactable element. In at least one example, the user computingdevice 104 can interact with the interactable element by scanning,reading, or otherwise interacting with the interactable element. Theuser computing device 104 can send an indication of the interaction tothe service provider server(s) 102 and the application managementcomponent 114 can receive the indication.

As described above, instant applications can be discoverable. In someexamples, instant applications can be discoverable via an interactableelement associated with a particular application (or a part thereof). Insome examples, an instant application can be discoverable via a bannerassociated with a web page, a link in a message, a map user interface, alibrary of recently used instant applications, or the like. In someexamples, instant applications can be discoverable based at least inpart on a geolocation of a user computing device, a time, a date, anevent, etc. Input associated with the banner, link, map user interface,library, etc. can cause an indication of an interaction with theinteractable element to be sent to the service provider server(s) 102.In some examples, the indication of the interaction with theinteractable element can be first sent to the third-party server(s) 108,which can send the indication of the interactable element to the serviceprovider server(s) 102.

At operation 312, the application management component 114 can cause auser interface associated with the instant application to be presentedvia the user computing device 104. In at least one example, based atleast in part on receiving the indication of the interaction, theapplication management component 114 can determine which instantapplication the indication is associated with and can cause the instantapplication to be downloaded or otherwise provided to the user computingdevice 104. The instant application can present the user interface 128such that the user 106 can interact with the instant application via theuser interface 128. The process 300 can continue at operation 210,described above with reference to FIG. 2, wherein the applicationmanagement component 114 can facilitate the remaining part(s) of theapplication being downloaded on the user computing device 104 (or not).

FIG. 4 illustrates an example process 400 for selecting an instantapplication based at least in part on context data associated with auser computing device and causing a user interface associated with theselected instant application to be surfaced via the user computingdevice.

At operation 402, application(s) 120 can be stored in a repository(e.g., the data store(s) 118) associated with a service provider, asdescribed above with reference to operation 202 of FIG. 2.

At operation 404, the application management component 114 can generatean interactable element associated with at least one instant applicationof the application(s) 120. As described above, an interactable element,which can include an identification code, can comprise a QR code, a RFIDtag, a barcode, an NFC tag, a URI, an image, etc. In some examples, aninteractable element can be a multi-function interactable element thatcan be associated with multiple instant applications. In some examples,an interactable element—multi-function or not—can be affixed to, orotherwise associated with, physical objects, such as tables, designatedseating areas, receipts, bicycles, scooters, vehicles, doors, itemsoffered for sale, etc. In some examples, an interactable element can bepresented via a computing device. In at least one example, interactableelement(s) associated with a part of an application (e.g., an instantapplication) can be mapped to, or otherwise associated with, the part ofthe application in the data store(s) 118.

At operation 406, the application management component 114 can receive,from a user computing device 104, an indication of an interaction withthe interactable element. In at least one example, the user computingdevice 104 can interact with the interactable element by scanning,reading, or otherwise interacting with the interactable element. Theuser computing device 104 can send an indication of the interaction tothe service provider server(s) 102 and the application managementcomponent 114 can receive the indication.

As described above, instant applications can be discoverable. In someexamples, instant applications can be discoverable via an interactableelement associated with a particular application (or a part thereof). Insome examples, an instant application can be discoverable via a bannerassociated with a web page, a link in a message, a map user interface, alibrary of recently used instant applications, or the like. In someexamples, instant applications can be discoverable based at least inpart on a geolocation of a user computing device, a time, a date, anevent, etc. Input associated with the banner, link, map user interface,library, etc. can cause the indication of the interactable element to besent to the service provider server(s) 102. In some examples, theindication of the interactable element can be first sent to thethird-party server(s) 108, which can send the indication of theinteractable element to the service provider server(s) 102.

At operation 408, the application management component 114 can select,based at least in part on the indication, an instant application tosurface to the user computing device 104. In at least one example, basedat least in part on receiving the indication of the interaction, theapplication management component 114 can determine which instantapplication the indication is associated with and can select the instantapplication based on the indication. In some examples, if theinteractable element is associated with a multi-function interactableelement, the application management component 114 can utilize contextdata to determine which instant applications associated with themulti-function interactable element to select. In at least one example,the context determination component 116 can determine context dataresponsive to receiving the indication of the interactable element. Thatis, in some examples, the receipt of the indication of the interactableelement can initiate a process to determine and/or select which instantapplication to provide to the user computing device 104.

At operation 410, which can be optional, the context determinationcomponent 116 can determine context data associated with a usercomputing device 104 of a user 106, as described above with reference tooperation 204 of FIG. 2. In some examples, the instant applicationselected in operation 408 can be selected further based at least in parton the context data, as described above.

At operation 412, the application management component 114 can cause auser interface associated with the instant application to be presentedvia the user computing device 104. In at least one example, based atleast in part on selecting an instant application, the applicationmanagement component 114 can cause the instant application to bedownloaded or otherwise provided to the user computing device 104. Theinstant application can present the user interface 128 such that theuser 106 can interact with the instant application via the userinterface 128. The process 400 can continue at operation 210, describedabove with reference to FIG. 2, wherein the application managementcomponent 114 can facilitate the remaining part(s) of the applicationbeing downloaded on the user computing device 104 (or not).

As described above, in some examples, multiple instant applications canbe available to the user computing device. In some examples, two or moreinstant applications can be associated with particular, discretefunctionalities that can be performed serially and/or in a sequence (andwithout the user needing to download the full application). FIG. 5illustrates an example process 500 associated with determining asequence of instant application(s) to surface via a user computingdevice.

At operation 502, application(s) 120 can be stored in a repository(e.g., the data store(s) 118) associated with a service provider, asdescribed above with reference to operation 202 of FIG. 2.

At operation 504, the context determination component 116 can determinecontext data associated with a user computing device 104 of a user 106,as described above with reference to operation 204 of FIG. 2.

At operation 506, the application management component 114 candetermine, based at least in part on the context data, a sequence ofinstant application(s), wherein the sequence is established through asequence of interactable element(s). In at least one example, theapplication management component 114 can utilize the context data todetermine a sequence of instant application(s). In some examples,previously downloaded instant applications can be used as context datafor selecting one or more subsequent instant applications and/or asequence of instant application(s). As an example, based at least inpart on a user downloading a first instant application associated with afirst merchant, the context determination component 116 can cause asecond instant application associated with a second merchant to besequentially and automatically (e.g., without further user input)downloaded on the user computing device 104. In at least one example,the second instant application can be associated with a promotion,incentive, reward, or the like to encourage the user to patronize thesecond merchant. For instance, the second instant application can offeran incentive for making an appointment with and/or purchase from thesecond merchant and can present a user interface to enable the user tomake the appointment. Additional or alternative examples are providedbelow.

In some examples, a sequence can be determined by the memory and/ornetwork constraints, such that, for example, the first and then thesecond application, or parts thereof, are downloaded based on memoryavailability of the user computing device 104. In some examples, theformatting of the applications, or parts thereof, can be adjusted basedon device data and attributes. For example, the second application, orpart thereof, may be formatted more than the first application, or partthereof.

In some examples, a sequence of instant application(s) can be designatedby a developer of an application with which the instant application(s)are associated. In some examples, a sequence of instant application(s)can be determined based at least in part on interaction data associatedwith users associated with the service provider. Such interaction datacan indicate which instant application(s) users interact with and inwhich order. Trends associated with sequences of instant application(s)can be associated with context data, which can be used by theapplication management component 114 for determining a sequence ofinstant application(s).

At operation 508, the application management component 114 can causeuser interface(s) associated with the instant application(s) to bepresented via the user computing device 104 based at least in part onthe sequence. In at least one example, each user interface enables auser 106 of the user computing device 104 to input data for enabling theparticular, discrete functionality associated with each of the instantapplication(s). Further, in at least one example, a portion of thecontext data can be used to customize a user interface associated withan instant application for the user 106. In at least one example, basedat least in part on receiving an indication of an interaction with aninteractable element corresponding to an instant application, theapplication management component 114 can cause a user interfaceassociated with the corresponding instant application to be presentedvia the user interface 128 of the user computing device 104. The user106 can interact with the user interface 128 to provide input associatedwith the corresponding instant application. In some examples, inputreceived via a first user interface associated with a first instantapplication can be used to customize and/or personalize a second userinterface, subsequently presented via the user computing device 104 inassociation with a second instant application.

In at least one example, the application management component 114 cancause interactable element(s) associated with instant application(s) tobe surfaced on the user computing device 104 based at least in part onthe sequence. As described above, in some examples, the interactableelement(s) can be surfaced via a text message, email, push notification,or the like. In some examples, the interactable element(s) can bepresented via another user computing device (e.g., a buyer-facingdisplay of a point-of-sale device, a merchant computing device, a kiosk,etc.). In some examples, the sequence of interactable element(s) can besurfaced at the same time or serially (e.g., one at a time). In someexamples, the interactable element(s) can be printed and/or otherwiseassociated with a physical medium (e.g., a physical object) forpresentation, instead of, or in addition to, the interactable element(s)being presented via the user computing device 104. In some examples, theapplication management component 114 can surface the instantapplication(s) dynamically and/or intelligently based at least in parton the sequence without causing associated interactable element(s) to besurfaced on the user computing device 104 and/or via another medium. Insuch examples, the user interface(s) can be presented based at least inpart on the context data determined at operation 504 and/or based oninput received via user interface(s) presented in association with thesequence.

FIG. 6 illustrates an example process 600 for persisting data obtainedduring a session associated with an instant application and transmittingat least a portion of the data to a user computing device when a fullapplication associated with the instant application is downloaded to theuser computing device.

At operation 602, application(s) 120 can be stored in a repository(e.g., the data store(s) 118) associated with a service provider, asdescribed above with reference to operation 202 of FIG. 2.

At operation 604, the context determination component 116 can determinecontext data associated with a user computing device 104 of a user 106,as described above with reference to operation 204 of FIG. 2.

At operation 606, the application management component 114 can select,based at least in part on the context data, an instant application tosurface via the user computing device 104, the instant application beingassociated with the part of the application. Details associated withselecting an instant application are described above with reference tooperation 206 of FIG. 2.

At operation 608, the application management component 114 can cause auser interface 128 associated with the instant application to bepresented via the user computing device 104. In at least one example,the application management component 114 can send instructions and/orcode related to the selected instant application over the network(s) 110to enable the user computing device 104 to provisionally or temporarilydownload the instant application. Functionality associated with theinstant application can be made available “on demand” or in near-realtime. As such, the user can quickly access the functionality, withouthaving to download the entire application. In at least one example, theinstant application can present a user interface, which can enable theuser 106 of the user computing device 104 to input data for enabling aparticular, discrete functionality associated with the instantapplication. In some examples, a portion of the context data can be usedto customize and/or personalize the user interface for the user 106.

At operation 610, the application management component 114 can obtain anindication that the user 106 intends to download an applicationassociated with the instant application, wherein downloading theapplication unlocks a set of functionalities larger than thoseassociated with the instant application. As described above, an instantapplication can be associated with a particular, discrete functionalityof an application. That is, the application can have a set offunctionalities that are larger than the particular, discretefunctionality with which the instant application is associated. In someexamples, the application management component 114 can receive anindication that the user 106 intends to download the applicationassociated with the instant application onto the user computing device104. In some examples, such an indication can be a request. In someexamples, the indication can be provided via an input to the userinterface 128.

At operation 612, in response to the indication, the applicationmanagement component 114 can persist data obtained during at least onesession and/or during an interaction with the instant application. Thatis, based at least in part on receiving the indication that the user 106intends to download the application, the application managementcomponent 114 can store data input to the instant application. In someexamples, the data can be associated with a session and/or aninteraction with the instant application.

At operation 614, the application management component 114 can use aportion of the data obtained during at least one session and/or duringan interaction with the instant application to obtain additional dataassociated with the user. In some examples, the portion of the data canbe a name and password. In some examples, the portion of the data can bepayment data. In some examples, the portion of the data can be anaddress (e.g., for delivery). Additional examples of data that can beprovided via the user interface presented by the instant application aredescribed below. In at least one example, the application managementcomponent 114 can use the portion of data to perform a look-up of, orotherwise search, the data store(s) 118 to obtain additional dataassociated with the user. For example, if a name or password isprovided, the name and/or password can be used to obtain data associatedwith a user profile to which the name and/or password correspond. In anadditional or alternative example, if payment data is provided, thepayment data can be used to obtain data associated with a user profileto which the payment data corresponds. In an additional or alternativeexample, if an address is provided, the address can be used to obtaindata associated with a user profile to which the address corresponds.

At operation 616, the application management component 114 can packagethe additional data and transmit it to the user computing device 104 inassociation with causing the application to be downloaded onto the usercomputing device 104, wherein the additional data can be used tocustomize and/or personalize the application and/or data presented via auser interface associated therewith. In at least one example, theapplication management component 114 can utilize the additional data tocustomize and/or personalize the application and/or the user interfaceassociated therewith.

Instant applications can be useful for a variety of merchant-facingand/or buyer-facing scenarios. As described above, in at least oneexample, an application, as described herein, can be associated with abuyer-facing application, a buyer application, or the like. One or moreinstant applications can be associated with the buyer-facing applicationsuch that when individual of the instant applications are downloaded bythe user computing device 104, different functionalities associated withthe buyer-facing application, the buyer application, or the like can beavailable to a buyer.

In at least one example, an instant application can enable a buyer toview one or more merchants and can provide an entry point for the buyerto order from individual of the one or more merchants. That is, theportion of the application executable by the user computing device 104can cause a user interface, such as the user interface 128, to bepresented that includes one or more user interface elements associatedwith one or more merchants. When a buyer interacts with a user interfaceelement, the instant application can enable a buyer to access a menu, anelectronic catalog or lookbook (e.g., associated with item data), anapplication site (e.g., content associated with a progressive webapplication), or the like associated with the corresponding merchant. Insome examples, such data can be presented via an augmented realitydevice associated with the user computing device 104. In some examples,the instant application can enable the buyer to place an order via aninteraction with the menu, catalog or lookbook, application site, or thelike. In some examples, different instant applications can facilitateeach of the functionalities and/or tasks described above. In someexamples, a single instant application can facilitate each of thefunctionalities and/or tasks described above.

In at least one example, an instant application can be downloaded andaccessible responsive to the user computing device 104 scanning,reading, or otherwise interacting with an interactable elementassociated with an item. In at least one example, related items and/oralternative items can be presented via the instant application (and/or auser interface associated therewith). That is, the portion of theapplication executable by the user computing device 104 can cause a userinterface, such as the user interface 128, to be presented that includesdata associated with related items and/or alternative items.

In at least one example, an instant application associated with themerchant and/or a service provider can enable a buyer to place an orderto purchase an item (e.g., good or service) from the merchant. That is,the portion of the application executable by the user computing device104 can cause a user interface, such as the user interface 128, to bepresented that includes one or more user interface elements with whichthe user 106 can interact to order an item from a merchant. For example,a buyer can use an instant application to place an order tablesideand/or via a contactless order in a dine-in experience. In anotherexample, an instant application can enable a buyer to place an orderfrom home or a remote location and can facilitate delivery and/orpick-up (e.g., curbside or in-store). In some examples, an instantapplication that facilitates ordering can be downloaded and/oraccessible based at least in part on determining that a buyer isproximate to a merchant, based at least in part on a buyer providing aninput to a map user interface identifying a geographic location ofinterest, or the like (e.g., based at least in part on context data).

In an additional or alternative example, an instant application can bepresented after a buyer has ordered an item and the instant applicationcan enable the buyer to checkout (e.g., provide payment data) on theuser computing device 104. In some examples, the user computing device104 can scan, read, or otherwise interact with an interactable elementassociated with a receipt or a checkout user interface that can cause aninstant application to be downloaded on a user computing device 104. Inat least one example, the instant application can cause a userinterface, such as the user interface 128, to be presented to enable thebuyer to provide payment data to pay for item(s) purchased via atransaction (e.g., via a contactless payment). In some examples, aninteractable element can be shared with a buyer (e.g., via a socialmedia post, text message, email, or the like) such that when the buyeraccesses an associated instant application, the buyer can providepayment data via the instant application (e.g., via a contactlesspayment).

In some examples, an instant application can be associated withobtaining payment data, for example, during a checkout or payment flow.In at least one example, the instant application can receive paymentfrom payment data stored on the user computing device 104, payment dataassociated with another application (e.g., a wallet), payment datastored remotely, or the like. In at least one example, the instantapplication can receive payment data via a payment instrument readerembedded in the user computing device 104 (e.g., an embedded paymentinstrument reader) and/or paired with the user computing device (e.g., apayment instrument reader device paired to the user computing device).In some examples, the instant application can receive payment data via asecure portal (e.g., via manual input to the secure portal). In exampleswhere the payment data is received via the instant application, theinstant application can send the payment data to the service providerserver(s) 102 for payment processing (e.g., via the merchant component112), as described below.

In some examples, an instant application can enable the buyer to splitpayments for a ticket with one or more other buyers. For instance, theportion of the application executable by the user computing device 104can cause a user interface, such as the user interface 128, to bepresented that enables the buyer to view a ticket associated with thebuyer and the one or more other buyers and the buyer can designate howto split the ticket and/or otherwise allocate a portion of the cost ofthe ticket to the one or more other buyers. In some examples, an instantapplication can enable the buyer to share item(s) associated with theirorder by presenting a URI (or other interactable element) that can beshared to other buyers. In such an example, the buyer can share the URIwith other buyers who can access the buyer's order. In an example, bysharing the URI, an instance of an instant application can be sharedwith other users.

Further, an instant application can enable a buyer to provide agratuity, sign up to receive receipts, collect loyalty, redeem loyalty,etc. That is, the portion of the application executable by the usercomputing device 104 can cause a user interface, such as the userinterface 128, to be presented that enables the buyer to provide agratuity, sign up to receive receipts, collect loyalty, redeem loyalty,etc. In some examples, an instant application can enable a buyer to pickup an order, track order status, return an item, exchange an item, orthe like. That is, the portion of the application executable by the usercomputing device 104 can cause a user interface, such as the userinterface 128, to be presented that enables the buyer to designate apick-up location for picking up an order, track order status, return anitem, exchange an item, or the like.

In at least one example, a buyer can use an instant application torequest a worker to visit a table or other designated seating area,reorder an item or items, etc. That is, the portion of the applicationexecutable by the user computing device 104 can cause a user interface,such as the user interface 128, to be presented that enables the buyerto request assistance from a worker, place another order, etc.

In some examples, an instant application can present push notifications(e.g., “your order is ready at the counter,” “your stylist is ready foryou,” etc.), recommendations, or the like. Moreover, an instantapplication can enable a buyer to identify themselves and/or share datawith a merchant.

In some examples, the instant application is associated with anincentive to purchase an item from another merchant within a geofence ofthe user computing device 104. In some examples, the incentive can beapplied to a stored balance maintained by a service provider (e.g., frompeer-to-peer payments or the like) and/or associated with an account ofthe user (e.g., associated with the service provider). That is, based atleast in part on receiving an indication that the user satisfied thecondition of the incentive (e.g., purchased an item from the othermerchant), the incentive can be applied to a stored balance maintainedby a service provider (e.g., from peer-to-peer payments or the like)and/or associated with an account of the user (e.g., associated with theservice provider). In some examples, such incentives can similarly beused for time or other context-based incentives.

In at least one example, an instant application can enable a buyer tobook an appointment with a merchant, rebook an appointment with amerchant, modify an appointment with a merchant, cancel an appointmentwith a merchant, or the like. That is, the portion of the applicationexecutable by the user computing device 104 can cause a user interface,such as the user interface 128, to be presented that enables the buyerto make (or rebook), modify, or cancel an appointment. Further, aninstant application can enable a buyer to make a reservation, rebook areservation, modify a reservation, cancel a reservation, or the like.That is, the portion of the application executable by the user computingdevice 104 can cause a user interface, such as the user interface 128,to be presented that enables the buyer to make (or rebook), modify, orcancel a reservation. In some examples, an instant application canfacilitate a payment flow for the appointment and/or reservation, or canpresent a gratuity user interface to enable the buyer to provide agratuity. In some examples, different instant applications canfacilitate each of the functionalities and/or tasks described above. Insome examples, a single instant application can facilitate each of thefunctionalities and/or tasks described above.

In at least one example, an application can be associated with amerchant-facing application, a merchant application, or the like. In atleast one example, an instant application can enable a user to clock-inand/or clock-out. That is, the portion of the application executable bythe user computing device 104 can cause a user interface, such as theuser interface 128, to be presented that enables a merchant or a workerassociated therewith (e.g., an employee, independent contractor, etc.)to clock-in and/or clock-out. In some examples, an instant applicationcan enable a merchant or a worker associated therewith to perform one ormore opening or closing procedures, log in to a point-of-saleapplication, or the like. That is, the portion of the applicationexecutable by the user computing device 104 can cause a user interface,such as the user interface 128, to be presented that enables a merchantor a worker associated therewith to declare cash tips, request cashtips, confirm completion of opening or closing procedures, providecredentials to access a point-of-sale application, or the like. In someexamples, different instant applications can facilitate each of thefunctionalities and/or tasks described above. In some examples, a singleinstant application can facilitate each of the functionalities and/ortasks described above. In some examples, each of the functionalitiesand/or tasks described above can be performed in a sequence (i.e.,serialized) by a user interacting with one or more instant applications.

In at least one example, an instant application can provide ademonstration. That is, the portion of the application executable by theuser computing device 104 can cause a user interface, such as the userinterface 128, to be presented that enables a merchant or a workerassociated therewith to view content associated with a demonstration.Furthermore, for a worker, an instant application can enable the workerto access an order based on proximity to a table or by scanning a code.Furthermore, a manager can access sales metrics, labor metrics, and/orother data that can be used for determining performance and/oridentifying opportunities for improvement. In some examples, a merchantcan view an appointment or reservation calendar using an instantapplication. Further, a merchant can use an instant application tocreate an appointment, add an item to an inventory or catalog, or thelike.

In some examples, an instant application can provide an access point toa peer-to-peer payment application. In such an example, an instantapplication can facilitate onboarding to the peer-to-peer paymentapplication. In some examples, an instant application can facilitate thecollection or redemption of rewards or loyalty via the peer-to-peerapplication.

As noted above, in some examples, different instant applications canfacilitate each of the functionalities and/or tasks described above. Insome examples, a single instant application can facilitate each of thefunctionalities and/or tasks described above. In some examples, each ofthe functionalities and/or tasks described above can be performed in asequence (i.e., serialized) by a user interacting with one or moreinstant applications.

Figures below illustrate example scenarios associated with instantapplications. The user interfaces described below can be presented viathe user interface 128 described above with reference to FIG. 1.Although described with reference to instant applications, techniquesdescribed herein can be applicable to full applications as well.

FIGS. 7A-7I illustrate an example of presenting an instant applicationto enable a user (e.g., worker such as an employee, independentcontractor, etc.) to perform a worker-specific task. In one example, theexample can be implemented for payroll management, such as to allowworkers (e.g., employees, independent contractors, etc.) to manage tipsor wages, or other worker-specific procedures. For example, aninteractable element 700, such as a QR code, can be displayed on adevice or via another medium, such as digital or analog receipts,invoices, etc., as shown in FIG. 7A. That is, FIG. 7A illustrates anexample interactable element 700 that can be presented for a worker of amerchant to perform a worker-specific task, such as adjusting tips. Insome examples, the interactable element 700 can be presented via amerchant computing device. In other examples, the interactable element700 can be presented on a sticker, panel, piece of paper, or otherphysical item. Additional or alternative interactable elements (e.g.,other than a QR code) can be used.

In at least one example, the interactable element 700 can have embeddedtherein transaction specific data, worker ID and passcode, payment proxy(e.g., a payment proxy having a particular syntax such as a monetarycurrency indicator prefixing one or more alphanumeric characters (e.g.,$Cash)), restaurant location, buyer data, etc., to allow the worker at amerchant location to reconcile the tips or daily wage data with thework. In some examples, such embedded data can be determined based atleast in part on context data. As shown in the example figure FIG. 7B,the worker can scan the interactable element 700 (e.g., using the usercomputing device 104), which can trigger the instant application withoutthe need for actual download of a full application. In at least oneexample, as illustrated in FIG. 7B, a user computing device 104 of theworker (e.g., the user 106) can scan, read, or otherwise interact withthe interactable element 700 and send an indication of the interactionto service provider server(s) 102. The service provider server(s) 102can cause a portion of an application (e.g., an instant application) tobe downloaded to the user computing device 104 responsive to receivingthe indication. Accordingly, the worker can access functionality forperforming a task.

FIG. 7C illustrates an example of a user interface element 702 that canbe presented by the instant application, which can enable the worker toadjust tips (e.g., the task). That is, in FIG. 7C, a user interfaceelement 702 associated with the instant application can be presented viathe user computing device 104. In some examples, the user interfaceelement 702 can be presented as a pop-up, overlay, or the like. In someexamples, a user interface, instead of a user interface element 702, canbe presented by the instant application.

In at least one example, the user interface element 702 can includeembedded data, which can be associated with relevant or contextual data(e.g., restaurant name), that can be presented to the worker. In atleast one example, the instant application can be associated with alimited set of functionalities (e.g., “adjusting tips”) to allow theworker to move money from a merchant account to a worker account (e.g.,a bank account of the worker, etc.). On interacting with the userinterface element 702, a user interface 704 can be presented via theuser computing device 104, as illustrated in FIG. 7D. In at least oneexample, the user interface 704 can present data associated withworker-specific payroll data, retrieved from a payroll component of theservice provider server(s) 102. In some examples, an interaction withthe user interface element 702 can cause the user interface 704 to bepresented automatically, e.g., through embedded passcode data in theinteractable element 700. Other examples may request the worker to enterthe passcode data via another user interface 706, as shown in FIGS. 7Eand 7F. In FIG. 7E, the instant application can request that the workerinput a passcode via a user interface 706, which the worker can do viaan interaction with the user interface 706, as illustrated in FIG. 7F.Responsive to providing the passcode, the instant application canpresent the user interface 704, as illustrated in FIG. 7D.

The user interface 704 can include user interface elements associatedwith payroll history data of the worker, as determined by the payrollcomponent of the service provider server(s) 102. In someimplementations, the application management component 114 can parsepayroll history data associated with the worker and surface data that ismost relevant to the worker, e.g., based on location, context, tips,table number, etc. In some implementations, the worker or a buyer canalso interact with the instant application on their devices to entercustom tips for a specific transaction, or adjust tips at a later time,as shown in FIGS. 7G-7I.

In some examples, the worker can select an individual transaction fromthe user interface 704 (e.g., of FIG. 7D) to adjust the tip as recorded.As illustrated in FIG. 7G, the worker can interact with one of the userinterface elements presented in association with the user interface 704(e.g., of FIG. 7D) to cause another user interface 708 to be presentedvia the user computing device 104. In an example, the user interfaceelement can be associated with a table served by the worker during theirshift (e.g., a transaction associated with said table). In at least oneexample, the user interface 708 can enable the worker to manually inputa tip amount (as illustrated in FIG. 7H), which can be associated withthe table/transaction, and presented via the user interface 704. Thatis, in FIG. 7I, the user interface 704 illustrates a tip associated withthe transaction corresponding to “Table 5,” wherein the user interface704 in FIG. 7D does not indicate a tip associated with the sametransaction.

In some examples, the user interface can include a selectable elementthat when selected can cause the full application associated with theinstant application to be downloaded on the user computing device. Insome examples, the worker may use the instant application to perform thetask and may not opt to download the full application.

FIGS. 8A-8I illustrate an example of presenting an instant applicationto enable a user (e.g., worker such as an employee, independentcontractor, etc.) to perform a worker-specific task. In one example, theexample scenario can be implemented with physical devices or Internet ofThings (IoT) devices, such as cash drawers and card readers. FIG. 8Aillustrates an example interactable element 800 that can be presentedfor a worker of a merchant to perform a worker-specific task, such asopening a cash drawer and/or counting application. In some examples, theinteractable element 800 can be presented via a merchant computingdevice. In other examples, the interactable element 800 can be presentedon a sticker, panel, piece of paper, or other physical item. Forexample, an interactable element 800, such as a QR code, can bedisplayed on a physical device, such as cash drawer, or another medium,such as a receipt, invoice, etc., as shown in FIG. 8A. Additional oralternative interactable elements (e.g., other than a QR code) can beused. In at least one example, the interactable element 800 can haveembedded therein device data, transaction data, worker ID andauthorization, merchant location, buyer data, etc., to allow a user 106(e.g., the worker) to physically interact with a hardware, such as acash drawer.

In at least one example, as illustrated in FIG. 8B, a user computingdevice 104 of the worker (e.g., the user 106) can scan, read, orotherwise interact with the interactable element 800 and send anindication of the interaction with the interactable element 800 to theservice provider server(s) 102. The application management component 114can cause a portion of an application (e.g., an instant application) tobe downloaded to the user computing device 104 responsive to receivingthe indication of the interaction with the interactable element 800.Accordingly, the worker can access functionality for performing a task.As shown in FIG. 8B, the worker can scan the interactable element toactivate the instant application without the need to download theapplication associated with the instant application. That is, techniquesdescribed herein can create a unique layer of software between one ormore hardware devices.

FIG. 8C illustrates an example of a user interface element 802 that canbe presented by the instant application, which can enable the worker toopen a cash drawer (e.g., the task). In at least one example, the userinterface element 802 can be presented as a pop-up, overlay, or thelike. In at least one example, the instant application can present auser interface instead of the user interface element 802. In someexamples, the user interface element 802 can include a selectableelement 804 that when selected, causes the cash drawer to be opened. Inat least one example, a user interface 806 can be presented to indicatethat an action is being performed (i.e., the cash drawer is beingopened), as illustrated in FIG. 8D. In some examples, the user interface806 can be presented automatically (e.g., based on detecting anactuation of the selectable element 804). In other examples, based atleast in part on detecting actuation of the selectable element, theinstant application can request that the worker input a passcode via auser interface 808, as illustrated in FIG. 8E, which the worker can dovia an interaction with the user interface 808, as illustrated in FIG.8F. Responsive to providing the passcode, the instant application canperform the task (e.g., open the cash drawer), and the user interface806 can be presented via the user computing device 104, as illustratedin FIG. 8D. That is, the instant application can send an instruction toa merchant computing device or other device associated with a cashdrawer to cause the cash drawer to open.

In at least one example, the user interface 802 can present relevant orcontextual data (such as merchant name) to the worker with a predefinedset of functionalities to allow the worker to interact with the hardwareand perform actions. The interactions with the hardware allow theservice provider server(s) 102 to respond to the interactions with asoftware action, such as determine the cash count in case of thehardware being a cash drawer. Example actions associated withtemporarily managing hardware, such as a cash drawer, are shown in FIGS.8G and 8H. FIGS. 8G and 8H illustrate an example of a user interface 810that can be presented to enable the worker to count cash and indicateamounts of cash via inputs to the user interface 810. In some examples,the user interface 810 can include a selectable element 812, which canbe selected to effectuate an action (i.e., “ending drawer”) and therebycause the flow to move from the instant application to specializedhardware. In at least one example, the data input to the user interface810 can be sent to the service provider server(s) 102 for at least oneof storing in the data store(s) 118 and/or synching with data stored inthe data store(s) 118.

FIG. 8I illustrates an example user interface 814 associated withmailing a cash drawer report to an intended recipient. In some examples,a report can optionally be generated within the instant application toshow, e.g., interaction history with the hardware, authorized users,etc., as shown in FIG. 8J. FIG. 8J illustrates an example user interface816 configured to present a cash drawer report, which can includedetails associated with when the report was run (e.g., time, date,etc.), the worker who ran the report, the starting amount of cash in thecash drawer, the ending amount of cash in the cash drawer, and the like.In some examples, authorized users can see contextual data, retrievedfrom merchant server(s) and/or the service provider server(s) 102. Insome implementations, the interactable element 800 can be used by theapplication management component 114 to help parse data and surface datathat is most relevant to the worker, e.g., based on location, context,time of the day, authorization level, etc., or propose some on-the-flyrecommendations within the instant application. In some examples, theuser interface 816 can include one or more selectable elements. Forinstance, a first selectable element 818 can enable the merchant torequest that the cash flow associated with the cash drawer be creditedto a first account (e.g., their “CashApp”) and/or a second selectableelement 820 can enable the merchant to request that the cash flow becredited to a second account (e.g., their “stored balance”). Actuationof such selectable elements can cause another application to beinitialized to allow the worker to perform a second set offunctionalities, such as settle cash flow from the cash drawer to their“CashApp,” their “stored balance,” or the like. In some examples, theuser interface 816 can include a selectable element 822 that whenselected can cause the report to be emailed to an email address of themerchant or the like. The worker can also interact with the userinterface 816 to perform specific actions, such as report tampering,etc.

In some examples, the user interface 816 can include a selectableelement that can be presented to prompt the worker to download the fullapplication. In some examples, the worker may use the instantapplication to perform the task and may not opt to download the fullapplication.

FIGS. 8A-8I are described with reference to hardware being a cashdrawer. In another example, if the hardware is a payment reader orkitchen display system executing on a computer, the instant applicationcan start a session of interaction with the hardware and tracktransactions during that session. This can be helpful for shiftmanagement, for example. In such examples, based at least in part ondetecting an interaction with the interactable element 900, the workercan be presented with a user interface that includes data associatedwith hardware data, and can therefore have the ability to interact andtrack interactions via the hardware.

FIGS. 9A-9H illustrate an example of presenting an instant applicationto enable a user (e.g., worker such as an employee, independentcontractor, etc.) to perform a worker-specific task. In one example, theexample scenario can be implemented for worker management, such as toallow workers to run shift reports or other close of day procedures. Forexample, an interactable element 900, such as a QR code, can bedisplayed on a device or another medium, such as receipts, invoices,etc., as shown in FIG. 9A. That is, FIG. 9A illustrates an exampleinteractable element 900 that can be presented for a worker of amerchant to perform a worker-specific task, such as running a shiftreport. In some examples, the interactable element 900 can be presentedvia a merchant computing device. In other examples, the interactableelement 900 can be presented on a sticker, panel, piece of paper, orother physical item. Additional or alternative interactable elements(e.g., other than a QR code) can be used. In at least one examples, theinteractable element 900 can have embedded therein transaction specificdata, worker ID and passcode, a payment proxy, merchant location, buyerdata, etc., to allow the worker at a merchant location to survey thepast, current and future shifts. In some examples, the embedded data canbe determined based at least in part on context data.

As shown in FIG. 9B, the worker can scan the interactable element, whichcan activate the instant application without downloading the applicationassociated with the instant application. In at least one example, asillustrated in FIG. 9B, a user computing device 104 of the worker (e.g.,the user 106) can scan, read, or otherwise interact with theinteractable element 900 and an indication of the interaction with theinteractable element 900 to the service provider server(s) 102. Theapplication management component 114 can cause a portion of anapplication (e.g., an instant application) to be downloaded to the usercomputing device 104 responsive to receiving the indication of theinteraction with the interactable element 900. Accordingly, the workercan access functionality for performing a task. FIG. 9C illustrates anexample of a user interface element 901 that can be presented by theinstant application, which can enable the worker to run a shift report(e.g., the task). In some examples, the user interface element 901 canbe presented as a pop-up, overlay, or the like. In at least one example,the instant application can present a user interface instead of the userinterface element 901.

In FIG. 9C, the user interface element 901 can present relevant orcontextual data (such as merchant name) to the worker with a predefinedset of functionalities (such as “run shift reports”) to allow the workerto monitor their own shifts or the shifts of other workers, such asthose reporting to them. In at least one example, the user interfaceelement 901 can include a selectable element 902 that, when selected,can cause another user interface 906 to be presented via the usercomputing device. That is, based at least in part on detecting aninteraction with the instant application, the worker can be presentedwith a user interface 906 that can include specific worker data,retrieved from merchant server(s) and/or service provider server(s) 102,as shown in FIG. 9D. The user interface 906 can present data associatedwith the worker's history as determined by merchant server(s) and/or theservice provider server(s) 102.

In some examples, the user interface 906 can be presented automatically(e.g., through embedded passcode data in the interactable element 900).In other examples, the instant application may request the worker toenter the authorization data as shown in FIGS. 9E and 9F. In FIG. 9E,the instant application can request that the worker input a passcode viaa user interface 908, which the worker can do via an interaction withthe user interface 908, as illustrated in FIG. 9F. Responsive toproviding the passcode, the instant application can present the userinterface 906 that illustrates shift details (e.g., time worked, breakstaken, total sales, total gratuities, open checks, time to close, and/orthe like), as illustrated in FIG. 9D. In some examples, the userinterface 906 presenting the shift report can include a selectableelement 910 that when selected, causes the shift report to be run and toclock out the worker. Based at least in part on actuating the selectableelement 910, the instant application can run the shift report and, insome examples, send the shift report to the service provider server(s)102. In some examples, the instant application can send an indication ofthe time to the service provider server(s) 102 to clock out the worker.FIGS. 9G and 9H illustrate example user interfaces 912 and 914 that canbe presented responsive to the worker actuating the selectable element910.

In some examples, the interactable element 900 can be used by theapplication management component 114 for parsing data and surfacing datathat is most relevant to the worker, e.g., based on location, context,tips, table number, etc., generate shift reports, or propose someon-the-fly recommendations within the instant application. In someimplementations, the worker can also interact with the instantapplication on the user computing device to perform specific actions,such as clock in or clock out, or adjust shifts, as shown in FIGS.9D-9F. In some implementations, when the selectable element 910 isselected, another instant application may be initialized to allow theworker to perform a second set of functionalities.

In some examples, the user interface 908 can include a selectableelement that can be presented to prompt the worker to download the fullapplication. In some examples, the worker may use the instantapplication to perform the task and may not opt to download the fullapplication.

FIG. 10 illustrates an example of a sequence of interactable elements(e.g., interactable elements 700, 800, and 900) that can be presented toenable a plurality of instant applications to be executed in aparticular sequence. In some examples, the application managementcomponent 114 can determine a sequence associated with a plurality ofinstant applications, as described above with reference to FIG. 5, andcan send a recommendation to a merchant computing device, for example,which can include the sequence. As such, the merchant can display theinteractable elements based at least in part on the recommendation. Insome examples, the interactable elements can be positioned proximate toone another (and/or other interactable elements) such that a worker caninteract with the interactable element serially to perform differenttasks, in some examples, without downloading a full application. In someexamples, the tasks (and thus interactable elements) and/or order of thetasks can be determined based at least in part on context data and/ordata associated with the worker, as described above.

In some examples, the application management component 114 can cause theinteractable elements to be presented via a computing device (e.g., amerchant computing device, a kiosk, etc.) based at least in part on thesequence. In at least one example, the application management component114 can maintain a sequence of such instant applications and triggeringactions (such as worker actions and/or interactions) can initializeinstant applications based at least in part on the sequence. Bypresenting interactable elements in a sequence, instant applications canbe initialized serially to accomplish a series of tasks. In someexamples, each of the interactable elements can be associated with amulti-function interactable element. In such an example, the applicationmanagement component 114 can utilize context data to determine whichinstant application to surface at a particular time, as described abovewith reference to FIG. 4.

FIGS. 11A-11G illustrate an example of automatically downloading andauthenticating a pre-configured application through an interactableelement presented via a merchant computing device 1100. For instance, inFIG. 11A, a worker can interact with a user interface 1102 presented bya dashboard on a point-of-sale application (e.g., via a display of themerchant computing device 1100) to use an interactable element tosign-in to the point-of-sale application and thus authenticate (withoutusing an email address and password, for example), which can enable theworker to accept payments and track sales per location (e.g., ofmerchant businesses). FIG. 11B illustrates a non-limiting example of auser interface 1104 that can be presented via the merchant computingdevice 1100 and can enable a merchant to customize their point-of-saleapplication and the use of instant applications associated therewith. Insome examples, the user interface 1104 can be presented via thepoint-of-sale application, or a part thereof (e.g., an instantapplication associated with the point-of-sale application). From amerchant perspective, the instant application can allow a merchant toview and present preset configurations, such as dashboard settings,pre-configured item combinations, preferred items/services to sell, cartconfigurations, security/authorization information, etc. Such actionsand/or functionalities can be configured by a merchant for their workersto see when they access instant application(s) of the merchant. FIG. 11Cillustrates a non-limiting example of a user interface 1106 that can bepresented via the merchant computing device 1100. The user interface1106 can present an interactable element 1108 that can be scanned, read,or otherwise interacted with (e.g., by a user computing device 104) toaccess the instant application.

In at least one example, a worker (e.g., a user 106) can use a usercomputing device 104 to scan, read, or otherwise interact with theinteractable element 1108. Based at least in part on scanning, reading,or otherwise interacting with the interactable element 1108, the usercomputing device 104 can send an indication of the interaction to theservice provider server(s) 102. The application management component 114can cause a portion of the point-of-sale application to be downloaded tothe user computing device 104 responsive to receiving the indication ofthe interaction with the interactable element 1108. The receipt of theindication of the interaction with the interactable element 1108 fromthe user computing device 104 can provide authentication and thus theportion of the point-of-sale application can be automatically downloadedand authenticated on the user computing device 104. The instantapplication can be associated with a user interface element 1110 thatcan be presented via a user interface 1111, as illustrated in FIG. 11D.In some examples, the user interface element 1110 can be presented as apop-up, overlay, or the like. In at least one example, the instantapplication can present a user interface instead of the user interfaceelement 1110.

In some examples, the instant application downloaded onto the usercomputing device 104 can provide a particular, discrete functionality(e.g. a limited version of the full point-of-sale application). In atleast one example, the point-of-sale application can determine whichdata can move from one computing device (e.g., the merchant computingdevice 1100) to another computing device (e.g., the user computingdevice 104, which can be a merchant's phone, handheld reader, or thelike) via an interaction with an interactable element, such as theinteractable element 1108. That is, the worker can access functionalityfor performing a task (without using an email address and password, forexample) with persistent data (e.g., worker settings, device code,worker preferences, worker dashboard configurations, full or condensedview of dashboard) transferred from the original device (e.g., themerchant computing device 1100) to a new device (e.g., the usercomputing device 104) through interaction with an interactable element(e.g., the interactable element 1108). The new device (e.g., the usercomputing device 104) can then have an instant application withpreconfigured settings within the instant application. In FIG. 11D, theuser interface element 1110 that can be presented by the instantapplication can enable the worker to sign-in to the point-of-saleapplication (e.g., the task) via interaction with a selectable element1112.

In at least one example, the user interface element 1110 can include aselectable element 1112 that when selected, provides an ability to theuser 106 to sign-in to a full application and a view into a fullapplication using the interactable element 1108 and embedded workerdata. In such an example, authentication data that was obtained prior tocreating the interactable element 1108, for example, as obtained via theuser interfaces 1102 and/or 1104 as shown in FIGS. 11A and 11B, can beembedded in the interactable element 1108 by the application managementcomponent 114 such that another device scanning, reading, or otherwiseinteracting with the interactable element 1108 (e.g., the user computingdevice 104) can also obtain the authorization data. Further, suchauthorization data can be used in subsequent launches of the sameinstant application, another instant application on the same usercomputing device 104 (e.g., determined using device identifiers), or thelike. In some examples, authorization can be conditional, timed, and/orvalid for a certain number of sessions or instant applications.

As illustrated in FIG. 11E, a worker can alternatively download thecomplete application via an interaction with a selectable element 1114presented via a user interface 1116 and enter a device code (e.g., aspresented via the user interface 1106 of FIG. 11C) instead of accessingapplication functionality via the instant application. FIG. 11Eillustrates the user interface 1116 that can be presented to prompt theworker to download the full application. In at least one example, afterthe user computing device 104 has downloaded the part of thepoint-of-sale application associated with the instant application, theservice provider server(s) 102 can prompt the worker to download thefull point-of-sale application. The instant application can detect inputindicating a request to download the full point-of-sale application andcan send an indication of such input to the service provider server(s)102. The application management component 114 can then cause the fullpoint-of-sale application to be downloaded onto the user computingdevice 104. The worker can then have access to all functionalityassociated with the point-of-sale application.

FIG. 11F illustrates a user interface 1118 that can be presented toenable the worker to clock-in or clock-out (e.g., functionality that maynot have been available via the instant application) but is availablevia the full point-of-sale application. FIG. 11G illustrates an exampleuser interface 1120 that can enable a worker to build an order, print abill, process payment, or the like (e.g., functionality that may nothave been available via the instant application) but is available viathe full point-of-sale application. In some examples, the graphical userinterfaces in FIGS. 11F and 11G can be presented by the fullpoint-of-sale application (after downloading onto the user computingdevice 104). In some examples, the graphical user interfaces in FIGS.11F and 11G can be presented by one or more other instant applications(e.g., if the worker does not download the full point-of-saleapplication).

FIGS. 12A-12F illustrate an example of cloning and downloading apre-configured application through an interactable element presented viaa merchant computing device 1200. FIG. 12A illustrates a user interface1202 that can (i) be presented via a merchant computing device 1200 and(ii) enable a worker of a merchant to build an order, print a bill,process payment, or the like. Such functionality can be available via apoint-of-sale application. In at least one example, a worker caninteract with the user interface 1202 to access a settings menu, asillustrated in FIG. 12B. The settings menu can be presented via a userinterface 1206. In at least one example, the worker can provide an inputto associate the same settings with another computing device (e.g.,clone the device settings of the merchant computing device 1200 onto asecond merchant computer device (e.g., the user computing device 104) atthe same location or different location). In at least one example, byproviding an input (e.g., selecting a selectable element or the like),the merchant computing device 1200 (e.g., an application executingthereon) can cause an interactable element 1208 to be presented via auser interface 1210 of the merchant computing device 1200, asillustrated in FIG. 12C. In at least one example, the interactableelement 1208 can have data embedded therein including workerauthorization data, dashboard configuration settings, device code,worker settings, device code, worker preferences, menus, devicesettings, full or condensed view of dashboard, etc. Such embedded datacan enable cloning and transporting such preferences and settingsautomatically and seamlessly to a new device (e.g., the user computingdevice 104) through interaction with the interactable element 1208. Thenew device (e.g., the user computing device 104) can then have aninstant application and/or full application downloaded thereon that canbe associated with preconfigured settings.

In at least one example, a second merchant computing device (e.g., theuser computing device 104) can scan, read, or otherwise interact withthe interactable element 1208 as presented via the first merchantcomputing device 1200, as illustrated in FIG. 12D. In at least oneexample, based at least in part on scanning, reading, or otherwiseinteracting with the interactable element 1208, the second merchantcomputing device (e.g., the user computing device 104) can send anindication of the interaction to the service provider server(s) 102. Theapplication management component 114 can cause a part of thepoint-of-sale application (e.g., an instant application) to bedownloaded to the second merchant computing device (e.g., the usercomputing device 104) responsive to receiving the indication. In atleast one example, the receipt of the indication from the secondmerchant computing device (e.g., the user computing device 104) canprovide authentication and thus the instant application associated withthe point-of-sale application can be automatically downloaded to thesecond merchant computing device (e.g., the user computing device 104)and authenticated. In at least one example, the instant application canbe associated with device settings that mirror the device settings ofthe first merchant computing device 1200.

FIG. 12E illustrates a user interface element 1212 that can be presentedby the instant application, which can enable the worker to install thepoint-of-sale application (e.g., the task). In some examples, the userinterface element 1212 can be presented as a pop-up, overlay, or thelike. In at least one example, the instant application can present auser interface instead of the user interface element 1212. In at leastone example, the user interface element 1212 can include a selectableelement 1214 that, when selected, can cause the full point-of-saleapplication to be downloaded onto the second merchant computing device(e.g., the user computing device 104).

FIG. 12F illustrates a non-limiting example of a user interface 1216that can be presented via the second merchant computing device (e.g.,the user computing device 104) to prompt the worker to download the fullapplication. The instant application can detect input indicating arequest to download the full point-of-sale application and can send anindication of such input to the service provider server(s) 102. Theapplication management component 114 can then cause the fullpoint-of-sale application to be downloaded onto the second merchantcomputing device (e.g., the user computing device 104). The worker canthen have access to additional functionality associated with thepoint-of-sale application. In at least one example, the point-of-saleapplication can be associated with the same device settings as the firstmerchant computing device 1200. That is, the second merchant computingdevice (e.g., the user computing device 104) can be a “clone” of thefirst merchant computing device 1200, as it pertains to settings of thepoint-of-sale application.

FIG. 13 illustrates an example wherein the user 106 can utilize the usercomputing device 104 to scan, read, or otherwise interact with aninteractable element 1300 presented, for example, via a user interface1302 of a merchant computing device 1304 to perform a buyer-facingfunctionality via an instant application associated with theinteractable element 1300. In some examples, the interactable element1300 can be associated with data, which can include a payment proxy,that can be embedded in the interactable element 1300 based at least inpart on context data. In an example, the instant application can beassociated with an ecommerce service associated with the serviceprovider. The instant application can enable a holistic checkoutexperience (e.g., to allow contactless payments) and facilitate areal-time buyer-facing display (e.g., for payments, for real-time cartbuilding, cart viewing, etc.). The movement of such functionality touser computing devices, such as the user computing device 104, canenable dynamic and personalized features for both buyers and merchantsregardless of whether such merchants have buyer-facing displaysassociated with merchant point-of-sale computing systems.

In at least one example, the instant application can enable the user 106to provide a tip via their own computing device (e.g., the usercomputing device 104), enroll in loyalty/rewards, manageloyalty/rewards, redeem loyalty/reward points, collect loyalty/rewardpoints, apply gift cards, apply coupons, review and/or modify an orderand/or cart (e.g., a virtual cart), pay with an application (e.g.,wallet application, peer-to-peer payment application, etc.) on their owncomputing device, and/or the like. In at least one example, the usercomputing device 104 can scan, read, or otherwise interact with theinteractable element 1300 and send an indication of the interaction withthe interactable element 1300 to the service provider server(s) 102. Theapplication management component 114 can cause a part of an application(e.g., an instant application) to be downloaded to the user computingdevice 104 responsive to receiving the indication.

In FIG. 13, a user interface element 1306 associated with the instantapplication can enable the user 106 to add a gratuity, e.g., as the cartis being built. In some examples, the user interface element 1306 can bepresented as a pop-up, overlay, or the like. In at least one example,the instant application can present a user interface instead of the userinterface element 1306. In some examples, the user interface element1306 can also include elements to enable the user 106 to view dataregarding associated taxes and shipping fees, if applicable, as the cartis being built. In at least one example, the instant application canhave additional functionalities to allow the user 106 to view and/ormodify a cart, apply rebates/coupons/loyalty/gift cards, etc. via a userinteraction with the user interface element 1306 in near real-time.Additional or alternative user interfaces can be presented to enable thebuyer to perform other operations as described above, including, but notlimited to, redeeming loyalty points, collecting loyalty points,reviewing and/or modifying an order and/or cart, paying with anapplication (e.g., wallet application, peer-to-peer payment application,etc.) on their user computing device 104, and/or the like.

FIG. 14 illustrates another example wherein the user 106 can utilize theuser computing device 104 to scan, read, or otherwise interact with aninteractable element 1400 presented to enable the user to provide a tipvia their own computing device, redeem loyalty points, collect loyaltypoints, review and/or modify an order and/or cart, pay with anapplication (e.g., wallet application, peer-to-peer payment application,etc.) on their user computing device, and/or the like. In some examples,the interactable element 1400 can be affixed to, or otherwise associatedwith, physical objects (e.g., a sticker, panel, piece of paper, physicalitem, etc.). In some examples, the interactable element 1400 can bepresented via an electronic device (e.g., a buyer-facing display of apoint-of-sale device, a user computing device, a kiosk, etc.). In someexamples, the interactable element 1400 can be associated with a receipt(e.g., physical receipt, digital receipt, or the like). In someexamples, interaction with the interactable element 1400 can cause aninstant application to be activated on the user computing device 104. Insome examples, the interactable element 1400 can be associated withdata, which can include a user identifier, account data, a paymentproxy, etc., that can be embedded in the interactable element 1400 basedat least in part on context data.

In at least one example, the user computing device 104 can scan, read,or otherwise interact with the interactable element 1400 and send anindication of the interaction with the interactable element 1400 to theservice provider server(s) 102. The application management component 114can cause a part of an application (e.g., an instant application) to bedownloaded to the user computing device 104 responsive to receiving theindication. FIG. 14 illustrates an example of a user interface element1402 that can be presented by the instant application. In some examples,the user interface element 1402 can be presented as a pop-up, overlay,or the like. In at least one example, the instant application canpresent a user interface instead of the user interface element 1402. Inat least one example, by interacting with a selectable element 1404associated with the user interface element 1402, the instant applicationcan present a user interface 1406, which can enable the user 106 to adda gratuity, redeem rewards, track an order status, review and/or modifyan order and/or cart, and/or the like. In some examples, an interactionwith the user interface 1406 can modify the order and/or cart during thetransaction (i.e., in near-real-time). Additional or alternative userinterfaces can be presented to enable the buyer to perform otheroperations as described above, including, but not limited to, redeemingloyalty points, collecting loyalty points, modify an order and/or cart,paying with an application (e.g., wallet application, peer-to-peerpayment application, etc.) on their user computing device 104, and/orthe like.

In an example where the interactable element 1400 is associated with areceipt, a merchant can also access the interactable element 1400 on thereceipt using a merchant computing device to perform certain actions,such as retrieve transaction data, validate a sale, initiate a return,track tips at the end of the day, reconcile receipts with financialsoftware, etc. In an example, the merchant component 112 can implementNFC, image recognition tools (camera), to manage physical and digitalreceipts.

In some examples, the user interface 1406 can indicate that the user 106earned rewards (e.g., loyalty points, a discount, etc.) and can promptthe user 106 to provide additional data (e.g., a phone number, emailaddress, etc.) to claim the rewards. Such data can be sent to theservice provider 102 server(s), stored in association with a profile ofthe user 106 (e.g., in the user data 122), and as such, the user 106 canuse the rewards for the current transaction or future transactions.

In at least one example, the user 106 can provide data, such as deviceidentifier, payment data, phone number or another identifier, tofacilitate customization and/or personalization of an instantapplication relevant to the user 106 using preloaded or pre-configureddata for a merchant, e.g., a merchant where the user is currentlyperforming a transaction, or where the user is currently paying for atransaction. For example, in response to a phone number, an instantapplication can be surfaced on the user computing device 104 withuser-merchant loyalty relationship. The loyalty/coupons can also besurfaced to incentivize the user 106 to download the full application.

In some examples, an instance of an instant application providingrewards and/or loyalty options can be embedded within an instant ornative application of a merchant. For example, if the user 106 isordering on an application or instant application of a merchant, a fieldmay be auto-populated with loyalty data obtained on-the-fly based onuser provided data, or user specific data learned from user data.

In at least one example, instant applications can be useful for itemverification, stock tracking, reordering, scan and track item data,product placement, and/or other inventory-based tasks. In some examples,an interactable element can link to inventory management. FIG. 15illustrates an example wherein a user 106 can utilize a user computingdevice 104 to scan, read, or otherwise interact with an interactableelement 1500 to enable the user 106 to manage and/or order inventory. InFIG. 15, the user 106 can be a merchant. In some examples, theinteractable element 1500 can be affixed to, or otherwise associatedwith, physical objects (e.g., a sticker, panel, piece of paper, physicalitem, etc.). In some examples, the interactable element 1500 can bepresented via an electronic device (e.g., a buyer-facing display of apoint-of-sale device, a user computing device, a kiosk, etc.). In someexamples, the interactable element 1500 can be proximate an item ofinventory (e.g., physically or via an ecommerce user interface). In atleast one example, the user computing device 104 can scan, read, orotherwise interact with the interactable element 1500 and send anindication of the interaction with the interactable element 1400 to theservice provider server(s) 102. The application management component 114can cause a part of an application (e.g., an instant application) to bedownloaded to the user computing device 104 responsive to receiving theindication.

FIG. 15 illustrates an example of a user interface element 1502 that canbe presented by the instant application, which can enable the user toorder a new item of inventory (e.g., by interacting with a selectableelement 1504 associated with the user interface element 1502). In someexamples, the user interface element 1502 can be presented as a pop-up,overlay, or the like. In at least one example, the instant applicationcan present a user interface instead of the user interface element 1502.In some examples, based at least in part on detecting actuation of theselectable element 1504, the instant application can present a userinterface 1506. The user interface 1506 can include user interfaceelements associated with item details, an indication of whether the itemis in stock, a price, a fulfillment mechanism, etc. In some examples,the instant application can enable the merchant to purchase newinventory, ask for help, find data associated with inventory items forpurchase and/or the like. In some examples, based at least in part onthe user 106 purchasing new inventory via the instant application, thenew inventory can be added to an inventory database associated with theservice provider.

The example provided above can be merchant facing. However, in someexamples, such an interactable element 1500 can be used by a buyer(i.e., can be buyer facing) to allow a buyer to obtain item data,determine where an item should be within a store, perform inventorytracking, get real-time updates on an item, receive an indication ofwhether the right item was picked (e.g., when compared to a wish list orshopping list), whether there are more options, purchase options,shipping and fulfilment options, etc.

FIG. 16 illustrates a plurality of interactable elements1600(A)-1600(N), which can represent different items and/or bundles ofitems that can be ordered and/or purchased via a scan, read, or otherinteraction with the interactable elements. In some examples, theplurality of interactable elements 1600(A)-1600(N) can be affixed to, orotherwise associated with, physical objects (e.g., a sticker, panel,piece of paper, physical item, etc.). In some examples, the plurality ofinteractable elements 1600(A)-1600(N) can be presented via an electronicdevice (e.g., a buyer-facing display of a point-of-sale device, a usercomputing device, a kiosk, etc.). In some examples, the sequence inwhich the plurality of interactable elements 1600(A)-1600(N) arepresented can be recommended and/or determined by the applicationmanagement component 114, as described above. In some examples, thesequence can be determined based on context data. In at least oneexample, the user 106 can utilize the user computing device 104 to scan,read, or otherwise interact with one of the interactable elementsillustrated in FIG. 16 to order and/or purchase the corresponding item.In some examples, such an order and/or purchase can be made via aninstant application.

FIG. 17 illustrates a plurality of interactable elements1700(A)-1700(N), which can represent different functionalities (e.g.,applet actions) that can be availed to the user 106 via the usercomputing device 104. In some examples, the plurality of interactableelements 1700(A)-1700(N) can be affixed to, or otherwise associatedwith, physical objects (e.g., a sticker, panel, piece of paper, physicalitem, etc.). In some examples, the plurality of interactable elements1700(A)-1700(N) can be presented via an electronic device (e.g., abuyer-facing display of a point-of-sale device, a user computing device,a kiosk, etc.). In some examples, the sequence in which the plurality ofinteractable elements 1700(A)-1700(N) are presented can be recommendedand/or determined by the application management component 114, asdescribed above. In some examples, the sequence can be determined basedon context data. In at least one example, the user 106 can utilize theuser computing device 104 to scan, read, or otherwise interact with aninteractable element to perform a corresponding task. In some examples,such a corresponding task can be performed via an instant application.

FIGS. 18A-18D illustrates a plurality of user interfaces associated withnotifications and/or data that can be presented via an instantapplication, for example, while the user 106 waits in line and/or for areservation (e.g., at a theme park, restaurant, spa, salon, etc.). In atleast one example, the user computing device 104 can scan, read, orotherwise interact with an interactable element 1800. In some examples,the interactable element 1800 can be affixed to, or otherwise associatedwith, physical objects (e.g., a sticker, panel, piece of paper, physicalitem, etc.). In some examples, the interactable element 1800 can bepresented via an electronic device (e.g., a buyer-facing display of apoint-of-sale device, a user computing device, a kiosk, etc.). In atleast one example, the user computing device 104 can send an indicationof an interaction with the interactable element 1800 to the serviceprovider server(s) 102. The application management component 114 cancause a portion of an application (e.g., an instant application) to bedownloaded to the user computing device 104 responsive to receiving theindication. In at least one example, and as illustrated in FIG. 18A, auser interface element 1802 associated with the instant application canbe presented via the user computing device 104. In some examples, theuser interface element 1802 can be presented as a pop-up, overlay, orthe like. In at least one example, the instant application can present auser interface instead of the user interface element 1802. In at leastone example, the user interface element 1802 can be associated with aselectable element 1804 to enable the user 106 to open the instantapplication. Based at least in part on detecting an actuation of theselectable element 1804, the instant application can present a userinterface 1806, which can present data to the user 106 while the user106 waits in line or awaits a reservation.

In some examples, data presented via the user interface 1806, can bebased at least in part context data. In some examples, the instantapplication and/or the application management component 114 can receiveupdated context data to track the user computing device 104 and cancause updated data to be presented via the user interface 1806 based atleast in part on receiving updated context data. In some examples, suchcontext data can include location data, a timestamp, a spot in line, orthe like. FIGS. 18B-18D illustrate different types of data that can bepresented via the user interface 1806. In some examples, another instantapplication or application can be embedded in the instant applicationallow the user to engage with another merchant or perform a differenttask while they are waiting. These kinds of embedded instantapplications or applications can be triggered, for example, by a devicestate or satisfaction of a condition.

FIGS. 19A-19F illustrate an example where a user 106 can utilize aninstant application to order a gift card (or other stored balance card).As illustrated in FIG. 19A, an instant application can present a userinterface element 1900 via the user computing device 104. In someexamples, the user interface element 1900 can be presented as a pop-up,overlay, or the like. In at least one example, the instant applicationcan present a user interface instead of the user interface element 1900.In some examples, the user interface element 1900 can be presented basedat least in part on the user computing device 104 interacting with aninteractable element. In some examples, the user interface element 1900can be presented based at least in part on context data associated withthe user computing device 106. In at least one example, the userinterface element 1900 can include a selectable element 1902 that, whenselected, can cause a user interface 1906 to be presented. The userinterface 1906 can enable the user 106 to access a menu of gift cards,amounts to be associated with a gift card, etc., as illustrated in FIG.19B. In some examples, the user 106 can select a gift card type, selectan amount of funds to be associated with the gift card, input a customamount for the gift card, select a recipient, or the like, asillustrated in FIG. 19C. While FIGS. 19A-19F are directed to gift cards,same or similar techniques can be applicable to any stored balance cardor payment instrument.

In at least one example, the user 106 can interact with the userinterface 1906 to select a selectable element. Based at least in part ondetecting a selection of the selectable element, the instant applicationcan present another user interface 1908 from which the user 106 canselect a contact as a recipient of a gift card. In at least one example,the instant application can request access to contacts of the user 106(e.g., as stored on the user computing device and/or as otherwiseassociated with the user) and the user can interact with the userinterface 1908, as illustrated in FIGS. 19D and 19E, to select arecipient of a gift card. In at least one example, the applicationmanagement component 114 can receive data from the instant application(e.g., associated with a request for a gift card) and can create a datastructure representative of the gift card (which can be associated withan identifier, an amount, etc.) based on such data. As illustrated inFIG. 19F, the user interface 1904 can include a selectable element 1910that when selected can cause the gift card, or an indication associatedtherewith, to be sent to a user computing device of the recipient.

The application management component 114 can send an indication of thegift card to a user computing device of the recipient. In some examples,the gift card can be accessible via an instant application. In oneimplementation, an instant application to enable the recipient to usethe gift card can be surfaced when certain conditions are met, forexample, when the recipient (i.e., the user computing device associatedtherewith) is at a location of a merchant whose gift card they have. Insome examples, a recommendation to use a gift card can be surfaced basedon natural language processing of actual conversations, textconversations, buyer chat conversations, and so on. In some examples, alink or other interactable element associated with a text message,email, push notification, etc. can be sent to the user computing deviceof the recipient and the recipient can access the gift card via the linkor other interactable element. In such examples, the gift card can beaccessed and/or redeemable via a web browser. In some examples, the giftcard can be accessible via a deep link in another application associatedwith the service provider. If the recipient does not have the otherapplication downloaded and/or an account to use the other application,the service provider can prompt the recipient to download theapplication to access the gift card.

While FIGS. 19A-19F are described in a buyer-facing example, in someexamples, same or similar techniques can be utilized by a merchant toorder gift cards (e.g., for sale via a brick-and-mortar store and/oronline). That is, the merchant can interact with a user interfaceassociated with an instant application to design gift cards, associatedbalances with the gift cards, and/or the like.

While examples described above include reference to presentation of auser interface element associated with an instant application that caninclude a selectable element, that when selected, causes a userinterface associated with the instant application to be presented, insome examples, the instant application can present the user interfacewithout first presenting the user interface element and/or selectableelement. Furthermore, while described as a user interface element above,such a user interface element can correspond to a user interfaceassociated with an instant application.

FIG. 20 illustrates an example process 2000 for nesting ofapplication(s) or part(s) thereof, within another application, or partthereof.

At operation 2002, a first instant application can detect engagementwith the first instant application. In at least one example, the firstinstant application can be associated with a first application. Thefirst application can be associated with a set of functionalities andthe first instant application can be associated with a smaller set offunctionalities than the first application. In some examples, the firstinstant application can be associated with a particular, discretefunctionality of the set of functionalities associated with the firstapplication.

In at least one example, the first instant application can present auser interface via the user computing device 104. The user interface canpresent data associated with the first instant application and canenable the user 106 to engage with the first instant application. Insome examples, the user interface can present one or more options forengaging with the first instant application. In at least one example,the first instant application can detect engagement with an optionpresented via the first instant application (e.g., from within the firstinstant application). In some examples, the user interface can be a homepage or main page that includes one or more options associated with oneor more merchants. For example, the home page or main page can be amarketplace, can offer coupons, rewards, or incentives from the one ormore merchants, or the like. In some examples, the user interface can beassociated with an activity user interface that includes one or moreoptions associated with one or more interactions or transactions of theuser 106. In some examples, each of the options can correspond to aninteraction or transaction and can be associated with parties to theinteraction or the transaction. For instance, if an option on theactivity user interface is associated with a previous transactionbetween the user 106 and a merchant, the option can be associated withthe merchant. In some examples, each of the options can be associatedwith an embedded application, or part thereof (e.g., an instantapplication), associated with the merchant. That is, in some examples,individual of the options can point to, via an embedding, deep link, orthe like, a merchant application, or part thereof. Additional detailsare provided below.

At operation 2004, the first instant application can trigger a secondinstant application to be initialized. In some examples, the secondinstant application can be associated with the first application and canbe associated with a different particular, discrete functionality or setof functionalities than the first instant application. In at least oneexample, the second instant application can be associated with a secondapplication that is different than the first application. The secondapplication can be associated with a set of functionalities and thesecond instant application can be associated with a smaller set offunctionalities than the second application. In some examples, thesecond instant application can be associated with a particular, discretefunctionality of the set of functionalities associated with the secondapplication.

In at least one example, based at least in part on detecting engagementwith the first instant application, the first instant application cantrigger the second instant application to be initialized. In someexamples, the option can be associated with an embedding, a deep link,or the like, such that upon detecting engagement with the option thefirst instant application can trigger initialization of the secondinstant application. In some examples, the second instant applicationcan be initialized without additional input from the user 106. In someexamples, the first instant application can present a user interfaceelement via the user interface prompting the user 106 to provide aninput to initialize the second instant application.

At operation 2006, the first instant application can transition to thesecond instant application. In at least one example, the first instantapplication can transition to the second instant application based atleast in part on initialization of the second instant application. In atleast one example, a user interface associated with the second instantapplication can be presented via the user computing device 104. The userinterface can present data associated with the second instantapplication and can enable the user 106 to engage with the secondinstant application. In some examples, the user interface can presentone or more options for engaging with the second instant application.

At operation 2008, the second instant application can determine whethera user interaction with the second instant application is detected. Inat least one example, the second instant application can determinewhether a user interaction with the second instant application isdetected. Based at least in part on determining that a user interactionwith the second instant application is detected (e.g., an interactionbetween the user and the user interface associated with the secondinstant application), the second instant application can cause a portionof the user interaction to be embedded in the first instant application.That is, the first instant application can receive an indication fromthe second instant application of the user interaction and, asillustrated at operation 2010, can embed the user interaction, or anindication thereof, in the first instant application. In at least oneexample, the second instant application can transition to the firstinstant application, as illustrated at operation 2012, and the firstinstant application can present the embedded portion on a user interfaceassociated with the first instant application, as illustrated atoperation 2014. In at least one example, a portion of an interactionwith the second instant application can be embedded in, or otherwiseassociated with, the first instant application. In such an example, theportion can be presented via the user interface presented by the firstinstant application. In at least one example, embedding application(s),part(s) thereof, and/or interaction(s) therewith into otherapplication(s), part(s) thereof, and/or interaction(s) therewith (i.e.,“nesting”) can ensure that either (a) the formatting of the embeddedapplication(s), part(s) thereof, and/or interaction(s) therewith, aspresented via a user interface, is based at least in part on theoriginating application(s), part(s) thereof, and/or interaction(s)therewith or (b) that the formatting of the embedded application(s),part(s) thereof, and/or interaction(s) therewith, as presented via auser interface, is different than the originating application(s),part(s) thereof, and/or interaction(s) therewith.

If the second instant application does not detect an interaction withthe second instant application, the second instant application cantransition to the first instant application, as illustrated at operation2016, and the first instant application can present a user interfaceassociated with the first instant application, as illustrated atoperation 2018. In such an example, the user interface may not includeany data indicative of user interaction with the second instantapplication.

In at least one example, if the application with which the first instantapplication is associated is downloaded to the user computing device,the embedded portion of the interaction with the second instantapplication can be embedded into the application. That is, in someexamples, the embedded portion of the interaction can be stored by theapplication management component 114 such that when the full applicationis downloaded, the embedded portion of the interaction can be associatedwith the application.

In some examples, the first instant application can transition to asecond application (e.g., instead of a second instant application). Insuch examples, interaction(s) with the second application can beembedded into the first instant application and presented via a userinterface presented via the first instant application. Further, in someexamples, a first application can transition to a second applicationand/or a part thereof. In such examples, interaction(s) with the secondapplication or part thereof can be embedded into the first applicationand presented via a user interface presented via the first application.That is, the process 2000 described above with reference to FIG. 20 canbe applicable for applications and/or instant applications alike.

In some examples, the first instant application can be associated with abuyer application (e.g., a peer-to-peer payment application, abuyer-facing application, a wallet application, an ecommerceapplication, or the like) that enables the user 106 to remit payment,redeem loyalty, redeem a coupon, input a gratuity, provide feedback, orthe like, and the second instant application can be associated with amerchant application that enables merchant-facing functionality such asbuilding a virtual cart, browsing an online store of a merchant, or thelike. In some examples, the first instant application can be associatedwith a merchant application that enables merchant-facing functionalitysuch as building a virtual cart, browsing an online store of a merchant,or the like and the second instant application can be associated with abuyer application (e.g., a peer-to-peer payment application, abuyer-facing application, a wallet application, an ecommerceapplication, or the like) that enables the user 106 to remit payment,redeem loyalty, redeem a coupon, input a gratuity, provide feedback, orthe like. In some examples, the first instant application can beassociated with a waitlist functionality that enables the user 106 toadd themselves to a waitlist of a restaurant, movie, attraction, etc.,and the second instant application can be associated with an orderingfunctionality that allows the user 106 to place an order for an item. Insome examples, the waitlist functionality and the ordering functionalitycan be associated with a same point-of-sale application of a merchant.In some examples, the waitlist functionality can be associated with anapplication associated with a first merchant and the orderingfunctionality can be associated with a second application of a secondmerchant.

FIGS. 21A-21L illustrate an example of transitioning between nestedapplication(s) or parts thereof. FIG. 21A illustrates an exampleinteractable element 2100 that can be presented for user 106 to performa task, such as ordering food and/or reserving a table via an instantapplication associated with a merchant. In some examples, theinteractable element 2100 can be presented via a user computing device(e.g., a buyer-facing display of a point-of-sale device, a merchantcomputing device, a kiosk, etc.). In other examples, the interactableelement 2100 can be presented on a sticker, panel, piece of paper, orother physical item. In at least one example, as illustrated in FIG.21A, the user computing device 104 can scan, read, or otherwise interactwith the interactable element 2100 and send an indication of theinteraction to the service provider server(s) 102. The applicationmanagement component 114 can cause a portion of an application (e.g., aninstant application) to be downloaded to the user computing device 104responsive to receiving the indication. Accordingly, the user 106 canaccess functionality for performing one or more tasks (e.g., ordering,joining a waitlist, ordering a gift card, purchasing merchandise, etc.)via interaction with a user interface. In some examples, the instantapplication can be downloaded, or otherwise surfaced, via the usercomputing device 104 without the user computing device 104 havinginteracted with the interactable element 2100. In some examples, theinstant application can be downloaded, or otherwise surfaced, via theuser computing device 104 intelligently based on context data associatedwith the user computing device 104. For instance, in a non-limitingexample, the application management component 114 can cause the instantapplication to be downloaded, or otherwise surfaced, via the usercomputing device 104 based at least in part on determining that the usercomputing device 104 is within a threshold distance of a location of amerchant.

FIG. 21B illustrates an example of a user interface element 2102 thatcan be presented by the instant application to enable the user 106 toaccess one or more options for interacting with the merchant. In someexamples, the user interface element 2102 can be presented as a pop-up,overlay, or the like. In some examples, a user interface, instead of auser interface element 2102, can be presented by the instantapplication. In at least one example, the user interface element 2102can include a selectable element 2104, that when selected, causes a userinterface 2106 to be presented, as illustrated in FIG. 21C. In at leastone example, the user interface 2106 can be presented by the instantapplication, which can enable the user 106 to select a task to perform(e.g., ordering, joining a waitlist, ordering a gift card, purchasingmerchandise, etc.). In some examples, the user interface 2106 caninclude one or more selectable elements associated with different tasks,that when selected, causes functionality for performing the task to beenabled via the instant application. For instance, if the user 106actuates a selectable element 2108 associated with joining a waitlist,the instant application can present one or more user interfaces toenable the buyer to join a waitlist.

FIGS. 21D-21F illustrate examples of such user interfaces. In at leastone example, based at least in part on detecting an input associatedwith the selectable element 2108, the instant application can cause theuser interface 2110 to be presented via the user computing device 104.In at least one example, the user 106 can input data (e.g., party size,name, phone number, etc.) via the user interface 2110. In at least oneexample, the user interface 2110 can include a selectable element 2112that when selected can cause the instant application to add the user toa waitlist associated with the merchant. The instant application cansend the data input via the user interface 2110 to the service providerserver(s) 102 and/or a local merchant computing device associated withthe merchant and the user 106 can be added to the waitlist (e.g., anindication of the buyer can be added to a data structure representativeof the waitlist). In at least one example, the instant application canpresent a user interface 2114 that can include a notification confirmingthat the user 106 has been added to the waitlist. The user interface2114 can include a selectable element 2116 that can be selected by theuser 106 to confirm receipt of such a notification.

In at least one example, the service provider server(s) 102 and/or thelocal merchant computing device can send a notification (e.g., email,text message, push notification, etc.) to the user computing device 104,as illustrated in FIG. 21G. That is, in FIG. 21G, a text message 2118 ispresented via a user interface of the user computing device 104. In atleast one example, based at least in part on detecting an interactionwith the text message, another application or instant application can beinitialized to enable the user 106 to view the contents of the textmessage 2118. In at least one example, the text message 2118 can includean interactable element 2120. Based at least in part on detecting aninteraction with the interactable element 2120, another instantapplication can be initialized. For instance, the interactable element2120 can point to an instant application to enable the user 106 toperform another task (e.g., order a drink, order food, select a table,etc.).

In some examples, the notification can be sent based at least in part oncontext data. For example, the notification can be sent based at leastin part on a location associated with the user computing device 104, aposition of the user 106 on the waitlist, a length of time that the user106 has been on the waitlist, or the like. In some examples, thenotification can be sent based at least in part on an interactionbetween the user computing device 104 and another interactable elementassociated with the instant application.

FIGS. 21I-21K illustrate example user interfaces to enable the user 106to order an item from the merchant. In at least one example, anotherinstant application can be initialized to enable the user 106 to performanother task. That is, based at least in part on detecting aninteraction with the notification or the interactable element 2120associated therewith, or based at least in part on receiving anindication of an interaction with another interactable elementassociated with the other instant application, the other instantapplication enabling ordering can be initialized. In some examples, theother instant application can be associated with the same application asthe first instant application. In some examples, the other instantapplication can be associated with a different application. In someexamples, if the applications are different, they can be associated witha same service provider. In some examples, if the applications aredifferent, they can be associated with different service providers.

FIG. 21I illustrates an example user interface element 2122 that can bepresented by the other instant application to enable the user 106 toplace an order. In some examples, the user interface element 2122 can bepresented as a pop-up, overlay, or the like. In some examples, a userinterface, instead of a user interface element 2122, can be presented bythe instant application. In at least one example, the user interfaceelement 2122 can include a selectable element 2124 that, when selected,causes a menu to be presented via the instant application. FIGS. 21J and21K illustrate an example of a user interface 2126 that can be presentedby the instant application to enable the user 106 to place an order. Inat least one example, the user 106 can interact with the user interface2126 to add one or more items to an order. In some examples, the userinterface 2126 can be updated to include an indication of which itemshave been ordered. In at least one example, the user interface 2126 caninclude a selectable element 2128, that when selected, can cause theinstant application to submit a request to order the items to theservice provider server(s) 102. In at least one example, the serviceprovider server(s) 102 can receive the order and send the order to amerchant computing device, front-of-house computing device,back-of-house computing device, kitchen display system, and/or the like.

In at least one example, the interaction with the user interface 2126presented via the other instant application can be provided to theinstant application associated with the user interface 2106 and at leasta portion of the interaction can be embedded in the instant applicationassociated with the user interface 2106. As such, the user interface2106 can present a user interface element 2130 that can represent atleast a portion of the interaction between the user 106 and the otherinstant application (i.e., the ordering instant application).

In at least one example, techniques described with reference to FIGS.21A-21L can be implemented in a retail or restaurant setting. Forexample, the interactable element 2100 can be presented, in a digital oranalog fashion, as shown in FIG. 21A. In at least one example, theinteractable element 2100 can have embedded therein device data,transaction data, merchant data, location, buyer data, etc., to allowthe user 106 (e.g., a diner, shopper, buyer, etc.) to perform actions,such as make appointments, make reservations, obtain real-time waitlistdata, shop at a retail location, adjust delivery options, requestcurb-side delivery, and so on. As described above with reference toFIGS. 21A-21L, the user 106 can cause an interaction between the usercomputing device 104 and the interactable element 2100 to join awaitlist, and at a later time, the user 106 can input orders to bedelivered when they arrive at their table or are otherwise sat at arestaurant. In at least one example, using at least context data (e.g.,from NFC and/or location-aware instant application, etc.), theapplication management component 114 can provide accurate and real-timedata, and predictive alerts to users, such as the user 106, and alsoenable optimized order-ahead functionalities (e.g., via applicationsand/or instant applications as described herein). As shown in FIG. 21A,the user 106 can scan, read, or otherwise cause an interaction with theinteractable element 2100 to activate the instant application withoutthe need for actual download, to order food or order at a table. In FIG.21C, embedded data can be presented via the user interface 2106. Suchdata can be relevant or contextual data (e.g., a merchant name). Theuser interface 2106, as described above, can enable the user 106 toperform a set of functionalities (e.g., “order” or “join waitlist”) toallow the user 106 to interact with the instant application and performspecific actions. On interacting with the interactable element 2100, theuser 106 can be presented with the user interface 2106 to provide input,say regarding waitlist, as shown in FIGS. 21D-21F. The data can berelayed along with an indication that it came through an instantapplication. The data obtained via the user interface 2106 can be usedto access and/or track user profile, profiles similar to user profile,to further personalize the experience either before or when the user 106is at the location of the merchant. In some examples, suchpersonalization or customization can be associated with a download of afull application associated with the instant application, future instantapplication(s) surfaced to the user 106, and/or data presented via thefull application and/or instant application(s).

The instant application described above, in at least one example, cantrack the user's data, such as location and how far the user 106 (e.g.,the user computing device 104) is from the merchant location and/ormerchant computing device of the merchant. This can allow a reservationcomponent associated with the service provider server(s) 102 and/orlocal merchant server(s) to detect in real-time whether the user 106will be able to make the appointment or reservation and if not,automatically modify their position on the waitlist (cancel if they havewalked too far away, move up or down if the distance does not match timeit takes to get back to the restaurant/merchant store). This kind ofintelligence can also be used to surface custom recommendations to theuser 106. For example, the service provider server(s) 102 can surface arecommendation to visit another merchant while the user 106 is on thewaitlist—this other merchant, as an example, can be one that is in thesame current location as the user 106, one with relatively manageablewait-time, or one that has some network/payment affiliation with themerchant, one that the user 106 usually visits (e.g., as determined byassociated user data), etc. In some examples, as shown in FIG. 21H, thereservation component can send action items to allow the user 106 tointeract with a second instant application, for example, to allow theuser 106 to order drinks or appetizers such that they are ready when theuser 106 arrives at the location of the merchant or is sat at theirtable. The timing of the notification sent to the user computing device104 and/or the timing of when the order is prepared/ready can bedependent on context data, such as the location of the user 106 (e.g.,user computing device 104) with respect to the merchant location.

As described herein, one instant application can be embedded withinanother instant application and can be triggered under certainconditions. In at least one example, a condition that can trigger atransition between instant applications can include a selection of anoption from a user interface of a first instant application, adetermination that a user 106 (e.g., user computing device 104) iswithin a threshold distance of the merchant location, etc. In at leastone example, the user 106 can interact with the second instantapplication, as shown in FIGS. 21I-21K, to place an order. In someexamples, to remit a payment, a same or a different instant applicationcan be surfaced. In at least one example, as described above, when theuser 106 orders items, such items can be ready when the user 106 arrivesat the merchant location and/or is sat at their table. In some examples,the menu items presented via the user interface 2126 can be determinedbased at least in part on contextual data, retrieved based on past buyerhistory, or other user data. For example, the item(s) presented, theorder of the items, or the like, can be personalized and/or customizedfor the user 106.

FIGS. 22A-22M illustrate an example process associated with ordering viaan instant application. In an example, as described above, instantapplications can be discoverable. In some examples, such discovery canbe based on context data including but not limited to location of a usercomputing device 104 of a user 106. In at least one example, a usercomputing device can be determined to be located within a thresholddistance (e.g., a geofence) of a merchant. Based at least in part ondetermining that the user computing device 104 is located within thethreshold distance of the merchant, the application management component114 can surface an instant application to the user computing device 104.In some examples, a user interface element 2200 associated with theinstant application can be presented via the user computing device 104,as illustrated in FIG. 22A. In some examples, the user interface element2200 can be presented as a pop-up, overlay, or the like. In someexamples, a user interface, instead of a user interface element 2200,can be presented by the instant application. In some examples, a textmessage, email, push notification, or the like, associated with theinstant application, can be received by the user computing device 104.In at least one example, the user 106 associated with the user computingdevice 104 can select a selectable element 2202 (e.g., “order now” orthe like) to download an instant application associated with theselectable element 2202. In another example, the user computing device104 can interact with an interactable element to cause the instantapplication to be downloaded on the user computing device 104.

In at least one example, a user computing device 104 can send anindication that the selectable element 2202 has been selected (or thatanother input has been detected) to the service provider server(s) 102.The application management component 114 can cause a part of anapplication (e.g., an instant application) to be downloaded to the usercomputing device 104 responsive to receiving the indication.Accordingly, the user 106 can access functionality for performing a task(e.g., placing an order), in some examples, prior to arriving at thephysical location of the merchant. In an example, a user interfaceelement 2204 can be presented by the instant application to enable theuser 106 to place an order, as illustrated in FIG. 22B. In someexamples, the user interface element 2204 can be presented as a pop-up,overlay, or the like. In some examples, a user interface, instead of auser interface element 2204, can be presented by the instantapplication. In at least one example, responsive to detecting an inputassociated with the instant application (e.g., selection of a selectableelement 2206 associated with the user interface element 2204), theinstant application can present a user interface 2208. The userinterface 2208 can present data associated with a menu from which theuser 106 can browse and place an order, as illustrated in FIG. 22C. Insome examples, the user interface 2208 can include additional detailsassociated with an order, such as a pick-up location, pick-up time, orthe like. In some examples, recommendations can be presented to the user106 and/or the user 106 can request assistance via the user interface2208.

In at least one example, the user 106 can interact with the userinterface 2208 to select item(s) to add to an order and, in someexamples, can pay for their item(s) via the instant application. FIG.22D illustrates an example user interface 2210 that can be presented bythe instant application to enable the user 106 to pay for item(s)ordered via the instant application. In at least one example, the userinterface 2210 can show a payment option as a peer-to-peer paymentapplication (if the peer-to-peer payment application is downloaded onthe user computing device 104), another previously downloaded paymentapplication, or another instant application corresponding to paymentfunctionality either related to the current instant application or onethat can be nested within the current instant application. That is, insome examples, the user interface 2210 can present an indication ofanother application, or part thereof, that is embedded in the currentinstant application. In some examples, an order summary can be presentedvia a user interface 2212 associated with the instant application, asillustrated in FIG. 22E, which can include user interface elements2214-2220 to enable the user 106 to continue shopping (e.g., placeanother order), view loyalty, and/or other order details (e.g., pick-updetails, order date and time, order number, etc.).

FIG. 22F illustrates another user interface 2222 that can be presentedby the instant application and/or an application, or part thereof,embedded in the instant application. In at least one example, the userinterface 2222 can present one or more user interface elements 2224,2226 associated with an offer for the merchant with whom the order isassociated and/or another merchant. For instance, the user interface2222 can present an offer for another merchant associated with theservice provider for use by the user 106. In some examples, the offercan be associated with the same merchant where an order was recentlyplaced. In some examples, the offer can be associated with another,different merchant associated with the service provider. In someexamples, the merchant component 112 and/or the buyer component 113 canselect offers for merchants that are within a threshold distance of alocation of the user computing device 104. In some examples, the offerscan be for a discount or other incentive. In some examples, the offerscan be time or location restricted. In some examples, the offers can bepresented via an embedded application or part thereof at the time theorder is place or at a later time. In some examples, the offers can beavailable via the full application at a later time.

FIG. 22G illustrates an example user interface 2228 associated with aninstant application that can include a selectable element, that whenselected, causes a full application to be downloaded on the usercomputing device 104. That is, another application, such as apeer-to-peer payment application, can be recommended to be downloaded(e.g., to remit payment for the order that is in progress). In someexamples, based at least in part on detecting a selection of theselectable element, the instant application can send an indication ofsuch to the service provider server(s) 102 and the applicationmanagement component 114 can cause the full application to be downloadedon the user computing device 104. In at least one example, after theother application (e.g., the peer-to-peer payment application) isdownloaded on the user computing device 104, when the user 106 accessesthe instant application and/or merchant application from which the user106 can place an order, data from the peer-to-peer payment applicationcan be downloaded and/or embedded in the user interface 2210 (e.g., as apayment option).

In an example, the user 106 can pay for the order initiated in theinstant application (e.g., associated with the merchant) through thepeer-to-peer payment application, which can be previously embedded inthe instant application or downloaded in association with the order. Inat least one example, after using the peer-to-peer payment applicationfor payment of the order, the user 106 can interact with a selectableelement (e.g., selectable element 2216) associated with the userinterface 2212, for example, to open an instant application or a fullapplication corresponding to the peer-to-peer payment application. Insome examples, the selectable element, which can be associated withloyalty, fulfillment, order status, or the like, can point to anembedded instant application and/or application. In some examples, basedat least in part on detecting an interaction with a selectable elementassociated with the user interface 2212, the instant application caninitialize another application and/or instant application. In anexample, the other application or instant application can be associatedwith the peer-to-peer payment application.

In an example, the peer-to-peer payment application, or part thereof,can present a user interface 2230 that can include user interfaceelements representative of interactions between the user 106 and thepeer-to-peer payment application, as illustrated in FIG. 22H. In someexamples, such an “activity user interface” can list at least a portionof a transaction history using the peer-to-peer payment application, orrelevant transactions performed using the peer-to-peer paymentapplication or a payment instrument associated with the payment option.In some examples, the user interface 2230 can present user interfaceelements to enable the user 106 to perform additional marketplaceactions, such as view order status, cancel order, etc. (e.g., instead ofthe application from where the order originated). In some examples,individual of the transactions presented in the transaction historyand/or relevant transactions performed using the peer-to-peer paymentapplication (e.g., as illustrated in the user interface FIG. 22H), canbe associated with selectable elements such that when selected, thepeer-to-peer payment application, or part thereof, can cause an instantapplication associated with the corresponding merchant to be surfacedvia the user computing device 104. In such an example, individual of theselectable elements can be associated with embedded applications, orparts thereof, deep links, or the like, which point to the otherapplications, or parts thereof. For instance, if the user 106 selects atransaction with Merchant A (e.g., by selection of a selectable element2232 associated with the transaction), the peer-to-peer paymentapplication can detect the input, send an indication of the input to theservice provider server(s) 102, which can cause an instant applicationassociated with the merchant (e.g., Merchant A) to be surfaced via theuser computing device 104, as illustrated by the example user interfacein FIG. 22I. The user 106 can then modify the transaction and/or placean order via the instant application associated with the merchant via aninteraction with the user interface 2234 shown in FIG. 22I. That is, inat least one example, the user 106 can initiate a new order or modify anexisting order through the user interface 2230, for example, byselecting a selectable element 2232 associated with a previoustransaction. Based at least in part on detecting a selection of theselectable element 2232, the peer-to-peer payment application, or a partthereof, can transition to an application, or part thereof, associatedwith the merchant. The application, or part thereof, associated with themerchant can present a user interface 2234 from which the user 106 canview details of previous transaction(s) with the associated merchant,start a new order, redeem rewards, or the like, as illustrated in FIG.22I.

FIG. 22J illustrates an example user interface 2236 that can bepresented by the application, or part thereof, which can confirm theorder and provide order details. In some examples, the user 106 cantrack the order via an interaction with the user interface 2236.

In some examples, the peer-to-peer payment application, or part thereof,can enable a user to modify a transaction and/or place a new order witha merchant without transitioning to another application, or partthereof. In such examples, functionality of the merchant can be embeddedor otherwise integrated in the peer-to-peer payment application.

FIG. 23 illustrates an example process 2300 for accessing instantapplication data via an application within which the instant applicationis embedded or otherwise associated.

At operation 2302, a buyer application can detect engagement from withinthe buyer application. In at least one example, the buyer applicationcan be associated with a set of functionalities that enable the user 106to remit payment, redeem loyalty, redeem a coupon, input a gratuity,provide feedback, or the like. In at least one example, the buyerapplication can be a peer-to-peer payment application that canfacilitate peer-to-peer payments between users of a peer-to-peerplatform. In some examples, the buyer application can be a mobilepayment application, a wallet application, or the like. In someexamples, the buyer application can be associated with one or moreinstant applications. In at least one example, the buyer application canbe associated with the service provider such that it can communicatewith the buyer component 113 on the service provider server(s) 102 toperform operations as described herein.

In at least one example, the buyer application can present a userinterface via the user computing device 104. The user interface canpresent data associated with the buyer application and can enable theuser 106 to engage with the buyer application. In some examples, theuser interface can present one or more options for engaging with thebuyer application. In at least one example, the buyer application candetect engagement with an option presented via the buyer application. Insome examples, the user interface can be a home page or main page thatincludes one or more options associated with one or more merchants. Forexample, the home page or main page can be a marketplace, can offercoupons, rewards, or incentives from the one or more merchants, or thelike. In some examples, the user interface can be associated with anactivity user interface that includes one or more options associatedwith one or more interactions or transactions of the user 106. In someexamples, each of the options can correspond to an interaction ortransaction and can be associated with parties to the interaction or thetransaction. For instance, if an option on the activity user interfaceis associated with a previous transaction between the user 106 and amerchant, the option can be associated with the merchant. In someexamples, each of the options can be associated with an embeddedapplication, or part thereof (e.g., an instant application), associatedwith the merchant. That is, in some examples, individual of the optionscan point to, via an embedding, deep link, or the like, a merchantapplication, or part thereof. Additional details are provided below.

At operation 2304, the buyer application can trigger an instantapplication associated with a merchant application to be initialized. Inat least one example, the merchant application can be associated with aset of functionalities to enable merchant-facing functionality such avirtual cart building functionality, a browsing functionality (e.g., ofan online store of a merchant), a waitlist functionality that enablesthe user 106 to add themselves to a waitlist of a restaurant, movie,attraction, etc., an ordering functionality that allows the user 106 toplace an order for an item. In some examples, the instant applicationcan be associated with a different particular, discrete functionality,which is part of the set of functionalities associated with the merchantapplication. As described above, in at least one example, the instantapplication and merchant application can be associated with a sameservice provider as the buyer application or a different serviceprovider than the buyer application (i.e., a third-party serviceprovider). In some examples, if the instant application and/or merchantapplication are associated with a third-party service provider, theapplication management component 114 can exchange data with the relevantthird-party server(s) 108 to facilitate operations described herein.

In at least one example, based at least in part on detecting engagementwith the buyer application, the buyer application can trigger theinstant application to be initialized. In some examples, such engagementcan be with an option from within the buyer application and the optioncan be associated with an embedding, a deep link, or the like. In atleast one example, detecting engagement with the option the buyerapplication can trigger initialization of the instant application. Insome examples, the instant application can be initialized withoutadditional input from the user 106. In some examples, the buyerapplication can present a user interface element via the user interfaceprompting the user 106 to provide an input to initialize the instantapplication.

At operation 2306, the buyer application can transition to the instantapplication. In at least one example, the buyer application cantransition to the instant application based at least in part oninitialization of the instant application. In at least one example, auser interface associated with the instant application can be presentedvia the user computing device 104. The user interface can present dataassociated with the instant application and can enable the user 106 toengage with the instant application. In some examples, the userinterface can present one or more options for engaging with the instantapplication.

In an alternative example, functionality associated with the merchantapplication can be accessed from within the buyer application. That is,the buyer application can have functionality associated with themerchant application embedded therein such that the user can access suchfunctionality without leaving the buyer application.

At operation 2308, the instant application can determine whether anindication of a transaction is received from the instant applicationand/or the merchant application. As described above, the instantapplication can be associated with a merchant application. In someexamples, the instant application and/or the merchant application (e.g.,if downloaded via the instant application) can enable the user 106 tobuild a virtual cart and/or otherwise participate in a transaction withthe merchant associated with the merchant application. In at least oneexample, the instant application and/or merchant application canfacilitate one or more steps of a payment flow to process payment forthe transaction. In such an example, the instant application and/or themerchant application can send an indication of the transaction and, insome examples, transaction data associated with the transaction. In atleast one example, the merchant application, and thus the instantapplication, can communicate with the buyer application and/or theservice provider server(s) 102 via an interface, such as an API or thelike. In some examples, the merchant application, and thus the instantapplication, can have buyer application functionality embedded therein(e.g., via an API or other integration mechanism) such that the merchantapplication processed payment for the transaction via the buyerapplication functionality. In at least one example, the indication canindicate such.

In some examples, the instant application and/or the merchantapplication can be integrated with the buyer application for paymentprocessing. That is, in some examples, the instant application and/orthe merchant application can allow users to use the buyer application toremit payment for transactions conducted using the instant applicationand/or the merchant application. In at least one example, the instantapplication and/or the merchant application can send an indication ofthe transaction to the buyer application with a request to processpayment for the transaction via the buyer application. In at least oneexample, the buyer application can send one or more communications tothe service provider server(s) 102 (e.g., the buyer component 113) toprocess payment for the transaction. In such an example, the buyerapplication and/or the buyer component 113 can send an indication ofwhether the payment was authorized or not to the instant application orthe merchant application. In some examples, the integrated buyerapplication functionality can cause the indication of the transactionand a request to process payment for the transaction to be sent to theservice provider server(s) 102 prior to, or instead of, sending therequest to the buyer application. In such an example, the buyercomponent 113 can process payment for the transaction and send anindication of such to the buyer application and the instant applicationand/or merchant application.

As described above, payment for the transaction can be performed via oneor more techniques. In some examples, buyer application functionalitycan be integrated in the instant application and/or merchantapplication. That is, there is no need to transition from the instantapplication and/or the merchant application to the buyer application. Insuch an example, buyer application functionality can be deep linkedand/or embedded into the instant application and/or the merchantapplication and/or a payment proxy can auto-populate into a paymentfield for processing payment for the transaction using buyer applicationfunctionality. In some examples, the merchant application can transition(back) to the buyer application for the buyer application to processpayment for the transaction.

At operation 2310, the buyer application and/or the service providerserver(s) 102 can cause the indication (of the transaction) to beassociated with stored activity of the user 106. In at least oneexample, the service provider server(s) 102 can store user data 122 inthe data store(s) 118. As described above, in some examples, a userprofile and/or a buyer profile can store indications of previousinteractions and/or transactions with one or more merchants. In anexample, the buyer application can send the indication of thetransaction, received from the instant application and/or the merchantapplication, to the service provider server(s) 102 (e.g., for paymentprocessing or otherwise) and the buyer component 113 can associate theindication with a user profile and/or buyer profile associated with theuser 106. In some examples, the service provider server(s) 102 canreceive the indication (e.g., prior to the buyer application receivingthe indication), associate the indication with the stored activity ofthe user 106, and send the indication to the buyer application. In suchan example, the buyer application may not cause the indication to beassociated with the stored activity of the user 106.

At operation 2312, the buyer application can present at least a portionof the stored activity data via an activity user interface of the usercomputing device 104. In at least one example, the instant applicationand/or the merchant application can transition back to the buyerapplication. In some examples, the user 106 can return to the buyerapplication after completing the transaction with the instantapplication and/or merchant application. In at least one example, whenthe buyer application is subsequently accessed, the buyer applicationcan present at least a portion of the stored activity data—which caninclude transaction data associated with the transaction between themerchant associated with the instant application and/or merchantapplication—via a user interface. That is, in at least one example,interaction(s) with the instant application and/or the merchantapplication can be embedded into the buyer application and presented viaa user interface presented by the buyer application. In at least oneexample, the buyer component 113 can send the portion of the storedactivity data to be presented via the user interface to the usercomputing device 104 for such presentation. In at least one example, theactivity user interface can present one or more transactions conductedby the user 106 using the buyer application and/or a payment instrumentassociated therewith. In some examples, individual of the transactions,when presented via the user interface, can be associated with trackingdata, fulfillment data, return data, and/or the like.

As described above, in at least one example, embedding application(s),part(s) thereof, and/or interaction(s) therewith into otherapplication(s), part(s) thereof, and/or interaction(s) therewith (i.e.,“nesting”) can ensure that either (a) the formatting of the embeddedapplication(s), part(s) thereof, and/or interaction(s) therewith, aspresented via a user interface, is based at least in part on theoriginating application(s), part(s) thereof, and/or interaction(s)therewith or (b) that the formatting of the embedded application(s),part(s) thereof, and/or interaction(s) therewith, as presented via auser interface, is different than the originating application(s),part(s) thereof, and/or interaction(s) therewith.

At operation 2314, the instant application and/or the merchantapplication can transition back to the buyer application. In at leastone example, the instant application and/or the merchant application cantransition back to the buyer application if no indication is receivedafter a period of time, the user 106 requests to return to the buyerapplication, and/or the like.

In some examples, the buyer application can transition to the merchantapplication (e.g., instead of the instant application). In suchexamples, interaction(s) with the merchant application can be embeddedinto the buyer application and presented via a user interface presentedvia the buyer application. Further, in some examples, a buyerapplication can transition to the merchant application. In suchexamples, interaction(s) with the merchant application can be embeddedinto the buyer application and presented via a user interface presentedvia the buyer application. That is, the process 2300 described abovewith reference to FIG. 23 can be applicable for applications and/orinstant applications alike.

FIGS. 24A-D illustrate an example for implementing the process 2300described above. FIG. 24A illustrates an example user interface 2400that can be presented via the user computing device 104. In at least oneexample, the user interface 2400 can be presented by a buyerapplication. In at least one example, the buyer application can beassociated with a set of functionalities that enable the user 106 toremit payment, redeem loyalty, redeem a coupon, input a gratuity,provide feedback, or the like. In at least one example, the buyerapplication can be a peer-to-peer payment application that canfacilitate peer-to-peer payments between users of a peer-to-peerplatform. In some examples, the buyer application can be a mobilepayment application, a wallet application, or the like.

In some examples, the user interface 2400 can be associated with anactivity user interface that includes one or more options associatedwith one or more interactions or transactions of the user 106. In someexamples, each of the options can correspond to an interaction ortransaction and can be associated with parties to the interaction or thetransaction. For instance, if an option on the activity user interfaceis associated with a previous transaction between the user 106 and amerchant, the option can be associated with the merchant. In an example,each of the options can be associated with a selectable element2402(A)-2402(N). In some examples, based at least in part on detectingengagement with the user interface 2400, such as via selection of aselectable element of the selectable elements 2402(A)-2402(N), the buyerapplication can trigger the initialization of an associated instantapplication and/or application. In some examples, each of the optionscan be associated with an embedded application, or part thereof (e.g.,an instant application), associated with a merchant with which thecorresponding transaction is associated. That is, in some examples,individual of the options can point to, via an embedding, deep link, orthe like, a merchant application, or part thereof.

FIG. 24B illustrates an example of a user interface 2404 that can bepresented based at least in part on the buyer application detectingselection of the selectable element 2402(B), which is associated withMerchant B. The user interface 2404 can be presented by a merchantapplication associated with Merchant B or an instant applicationassociated therewith. That is, the buyer application can detectselection of the selectable element 2402(B) and transition to themerchant application associated with Merchant B (or an instantapplication associated therewith). The merchant application associatedwith Merchant B can present the user interface 2404.

In at least one example, the user interface 2404 can enable the user 106to start a new order, for example, by interacting with a selectableelement 2406 on the user interface 2404. In at least one example, theuser 106 can interact with the user interface 2404, which can correspondto an online store of the merchant, to add one or more items to avirtual cart. FIG. 24C illustrates an example of a user interface 2408that can be presented by the merchant application, or a part thereof, toenable the user 106 to review the item(s) associated with the order. Asshown, item(s) associated with the order can be presented as userinterface element(s) associated with the user interface 2408. In atleast one example, the user interface 2408 can include a selectableelement 2410 that can enable the user 106 to remit payment. As describedabove, in some examples, based at least in part on detecting selectionof the selectable element 2410 the merchant application and/or partthereof can process payment for the transaction and send an indicationof the transaction to the buyer application. In some examples, themerchant application and/or part thereof can process payment usingpayment processing functionality associated with the buyer applicationthat is integrated in the merchant application. In some examples, themerchant application and/or part thereof can send an indication of thetransaction with a request to process payment for the transaction.

FIG. 24D illustrates the user interface 2400 from FIG. 24A. As describedabove, based at least in part on receiving the indication of thetransaction, the buyer application can cause the indication (of thetransaction) to be associated with stored activity of the user 106. Inat least one example, the service provider server(s) 102 can store userdata 122 in the data store(s) 118. As described above, in some examples,a user profile and/or a buyer profile can store indications of previousinteractions and/or transactions with one or more merchants. In anexample, the buyer application can send the indication of thetransaction, received from the instant application and/or the merchantapplication, to the service provider server(s) 102 (e.g., for paymentprocessing or otherwise) and the buyer component 113 can associate theindication with a user profile and/or buyer profile associated with theuser 106. In some examples, the service provider server(s) 102 canreceive the indication (e.g., prior to the buyer application receivingthe indication), associate the indication with the stored activity ofthe user 106, and send the indication to the buyer application. In suchan example, the buyer application may not cause the indication to beassociated with the stored activity of the user 106.

In at least one example, as described above, the buyer application canpresent at least a portion of the stored activity data via an activityuser interface of the user computing device 104. The user interface 2400can be the activity user interface. In at least one examples, when thebuyer application is subsequently accessed (e.g., after the user 106 hascompleted the transaction with the merchant), the buyer application canpresent at least a portion of the stored activity data—which can includetransaction data associated with the transaction between the merchantassociated with the instant application and/or merchant application—viathe user interface 2400. That is, in at least one example,interaction(s) with the instant application and/or the merchantapplication can be embedded into the buyer application and presented viathe user interface 2400 presented by the buyer application. The list oftransactions has been updated to include a new transaction with MerchantB. The selectable element 2412 can be associated with the newtransaction with Merchant B. In some examples, transaction detailsassociated with the transactions can be presented via the user interface2400. In at least one example, transaction details can be associatedwith selectable elements such that when selected, the buyer applicationcan present the transaction data to the user 106 via the user interface2400 (e.g., a pop-up, overlay, or the like) or via another userinterface.

In some examples, the user 106 can interact with the user interface 2400to access embedded applications or parts thereof by interacting withother selectable elements associated with the user interface 2400. Forexample, in some examples, one or more merchants with whom the user 106has previously interacted with, the user 106 has most recentlyinteracted with, have been recommended for the user 106, or the like canbe presented via one or more selectable elements 2414(A)-2414(N).

FIG. 25 illustrates an example process 2500 for causing data input viaan interaction with a user interface presented via an instantapplication on a first user computing device of a user to be presentedvia a user interface associated with a subsequently downloadedapplication on a second user computing device of the user.

At operation 2502, the application management component 114 can cause afirst user interface associated with an instant application to bepresented via a first user computing device of a user 106. In at leastone example, an instant application can be downloaded, or otherwisesurfaced, on a first user computing device of a user. In some examples,the instant application can be downloaded, or otherwise surfaced, basedat least in part on context data. That is, in at least one example, theapplication management component 114 can determine context dataassociated with the first user computing device and can cause theinstant application (and, thus the first user interface) to be presentedbased at least in part on the context data.

In some examples, the instant application can be downloaded, orotherwise surfaced, in response to an indication of an interactionbetween the first user computing device and an interactable elementassociated with the instant application. In some examples, theinteractable element can be affixed to, or otherwise associated with,physical objects (e.g., a sticker, panel, piece of paper, physical item,etc.). In some examples, the interactable element can be presented viaan electronic device (e.g., a buyer-facing display of a point-of-saledevice, a user computing device, a kiosk, etc.). In some examples, theinteractable element can be associated with a physical mailer, a pushnotification, an email, a text message, or the like. In some examples,an indication of an interaction between the first user computing deviceand the interactable element can be associated with an identifier, whichcan be encoded in the interactable element and/or otherwise associatedtherewith. In some examples, an indication of an interaction between thefirst user computing device and the interactable element can beassociated with identification data such as an account number of theuser 106, a physical address of the user 106, a telephone number of theuser 106, an email address of the user 106, and/or the like. In someexamples, such identification information can be encoded in theinteractable element and/or associated therewith.

As described above, the instant application can be associated with aparticular, discrete functionality, which can be part of a set offunctionalities associated with an application of which the instantapplication is a part. That is, the application can be associated with aset of functionalities that is larger than the particular, discretefunctionality of the instant application. The instant application canpresent a first user interface via the first user computing device.

At operation 2504, the application management component 114 can receivedata via an interaction with the first user interface. In at least oneexample, the user 106 can interact with the user interface to provide aninput. Data associated with such an input can be sent to the serviceprovider server(s) 102. In some examples, such data can be a name andpassword. In some examples, such data can be payment data. In someexamples, such data can be an address (e.g., for delivery). In someexamples, additional or alternative data can be input via theinteraction. In some examples, such data can be associated with anidentifier and/or identification data. In some examples, theidentification data can be received during the interaction.

At operation 2506, the application management component 114 can receive,from a second user computing device associated with the user 106, arequest to download an application with which the instant application isassociated. In an example, the user 106 can access the instantapplication on their mobile computing device but may desire to downloadthe associated application via their tablet computing device. In anotherexample, the user 106 can access the instant application on their tabletcomputing device but may desire to download the associated applicationon a merchant computing device. In at least one example, the second usercomputing device can send a request to download the application to theservice provider server(s) 102. In some examples, the request todownload can be received in association with an indication of aninteraction between the second user computing device and an interactableelement presented via the first user interface. In some examples, therequest can be associated with an identifier and/or identification data.

At operation 2508, the application management component 114 candetermine whether there is a correspondence between the data and therequest. In some examples, the application management component 114 cananalyze data received via the interaction and/or the request todetermine whether there is a correspondence between the data and therequest. That is, the application management component 114 can analyzethe data and/or the request to determine if there is a correspondencebetween the first user computing device and the second user computingdevice.

In some examples, the data and the request can be associated withidentifiers. For example, the interactable element can be associatedwith an identifier. That is, an identifier can be embedded in theinteractable element. In some examples, the mechanism throughout whichthe second request is received can be associated with the sameidentifier. For example, in some examples, the user 106 can cause aninteraction between the same interactable element and the second usercomputing device. In some examples, the instant application can providethe identifier and/or another interactable element encoded with theidentifier that can trigger the request for the application by thesecond user computing device. The application management component 114can determine whether a first identifier associated with the data and asecond identifier associated with the request are the same or otherwisecorrespond, the application management component 114 can determine acorrespondence between the data and the request, and thus the first usercomputing device and the second user computing device.

In some examples, the data and the request can be associated withidentification data (e.g., an account number, a physical address, atelephone number, an email address, a device identifier, or the like).In some examples, at least some identification data can be known by theapplication management component 114 prior to receiving the data and/orthe request. In some examples, at least some of the identification datacan be encoded in the interactable element. In some examples, theinteractable element can be mapped to, or otherwise associated with atleast some identification data. In some examples, identification datacan be provided via the first user interface. In some examples,identification data can be provided in association with the request. Insome examples, the application management component 114 can determinewhether first identification data associated with the data and secondidentification data associated with the request is associated with asame user (e.g., user profile). Based at least in part on determiningthat the first and second identification data are associated with thesame user, the application management component 114 can determine acorrespondence between the data and the request, and thus the first usercomputing device and the second user computing device.

In some examples, location data associated with the interaction andlocation data associated with the request can be received by theapplication management component 114. That is, in some examples, thedata received via the interaction with the first user interface can beassociated with first location data and the request can be associatedwith second location data. The application management component 114 candetermine whether the first location data and the second location datacorrespond to a same location and/or are within a threshold distance ofone another. Based at least in part on determining that the firstlocation data and the second location data correspond to a same locationand/or are within a threshold distance of one another, the applicationmanagement component 114 can determine a correspondence between the dataand the request, and thus the first user computing device and the seconduser computing device.

In at least one example, based at least in part on receiving the requestto download the application and determining there is a correspondencebetween the data and the request (and thus the first user computingdevice and the second user computing device), the application managementcomponent 114 can store session data of a session of the instantapplication. In some examples, the session data can be associated withthe data received via the interaction with the first user interface atoperation 2504. In at least one example, the session data can be used tocustomize the application and/or data presented via a user interfaceassociated with the application, that can be presented via the seconduser computing device.

The application management component 114 can receive the request and cancause the application to be downloaded on the second user computingdevice, as illustrated at operation 2508.

At operation 2510, the application management component 114 can causethe application to be downloaded on the second user computing device,wherein at least one of the application or a second user interfaceassociated with the application is customized based at least in part onthe data. In at least one example, based at least in part on determininga correspondence between the data and the request (i.e., “yes” atoperation 2508), the application management component 114 can customizeand/or personalize at least one of the application or the second userinterface with data received via the interaction with the first userinterface. In some examples, as described above, session data can beassociated with the application and can be presented via the second userinterface and/or used to customize and/or personalize data presented viathe second user interface. That is, in at least one example, sessiondata can be preserved from the first user computing device andtransferred to the second user computing device, while the applicationand/or the user interface associated therewith is customized and/orpersonalized for the second user computing device.

In some examples, the first user computing device and the second usercomputing device can be associated with different devicecharacteristics. In some examples, the second user computing device canpresent a user interface that is configured or otherwise presented basedat least in part on the device characteristic(s) of the second usercomputing device. For example, the second user computing device can beassociated with a different display, different display ratio, differentorientation, or the like than the first user computing device. In suchan example, the second user interface can be presented at least in parton the second user computing device characteristic(s), which may causethe second user interface to appear different than the first userinterface.

At operation 2514, the application management component 114 can causethe application to be downloaded on the second user computing device,wherein a second user interface associated with the application is notcustomized based on the data. In at least one example, if nocorrespondence is determined between the data received via theinteraction and the request, the application management component 114can cause the application to be downloaded on the second user computingdevice and can cause a user interface to be presented via theapplication, but the user interface may not be customized and/orpersonalized for the user 106.

As described below, in some examples, an instant application can beassociated with a payment functionality, wherein the applicationassociated therewith is associated with a payment processing service. Insome examples, an instant application can be associated with ademonstration of a service and the application associated therewith canbe associated with a full-scale offering of the service. Additionaldetails are provided below.

FIGS. 26A-26D illustrate an example of creating a mock experience (e.g.,a demonstration) for a user 106, such as a new merchant (e.g., amerchant new to the service provider). In FIG. 26A, the interactableelement 2600 is displayed in association with a physical mailer (e.g.,in analog fashion), but can be associated with an additional oralternative channel or medium. In at least one example, the interactableelement 2600 can have embedded therein, transaction data, merchant data,location data, buyer data, an identifier, etc., to trigger downloadingof an instant application that creates a mock or trial experience forthe merchant before the merchant decides to download the fullapplication, purchase software, purchase an item, etc. In some examples,the interactable element 2600 can have embedded therein data that haspredefined restaurant or retail settings. In at least one example, theuser 106 can scan, read, or otherwise interact with the interactableelement 2600, for example, using the user computing device 104. In atleast one example, the user computing device 104 can send an indicationof the interaction to the service provider server(s) 102 and theapplication management component can cause an instant applicationassociated with the interactable element 2600 to be downloaded, orotherwise surfaced on the user computing device 104. In at least oneexample, a user interface element 2602 associated with the instantapplication can be presented via the user computing device 104, asillustrated in FIG. 26B. In some examples, the user interface element2602 can be presented as a pop-up, overlay, or the like. In someexamples, a user interface, instead of a user interface element 2602,can be presented by the instant application.

In some examples, data embedded in the interactable element 2600 (e.g.,transaction data, merchant data, location data, buyer data, anidentifier, predefined restaurant or retail settings, etc.) can be usedto customized and/or personalize the user interface element 2602. Thatis, in at least one example, based at least in part on the user 106causing an interaction between the user computing device 104 and theinteractable element 2600, the instant application can be downloadedonto the user computing device 104. In at least one example, the user106 can interact with a selectable element 2604 presented via the userinterface element 2602 to initialize the demonstration, for example, ofhow software works and/or can be used. For example, as shown in FIG.26C, the instant application can present a user interface 2606, whichcan represent a mock restaurant floor layout. In some examples, the user106 can interact with the user interface 2606 to demo at least a part ofthe application with which the instant application is associated. Asanother example, as shown in FIG. 26D, the instant application canpresent a user interface 2608 that can demonstrate how a menu can bepresented. In some examples, the user 106 can interact with the userinterface 2606 to demo at least a part of the application with which theinstant application is associated. In some examples, such the userinterface 2606 and/or the user interface 2608 can include a selectableelement 2610 that when selected can cause the full application to bedownloaded on the user computing device 104. As described above, in someexamples, if the full application is downloaded, any data input into theinstant application can be transferred to the full application and, insome examples, can be used to customize and/or personalize theapplication and/or data presented via a user interface associatedtherewith. In some examples, the full application can be downloaded to adifferent user computing device. In some examples, as described above,based at least in part on determining a correspondence between the datainput to the instant application and the request to download the fullapplication on a different user computing device, data input viainteractions with the instant application can be transferred to the fullapplication and presented via a user interface on a different usercomputing device.

In some examples, the application management component 114 can obtainmerchant data, from the data store(s) 118 and/or third-party datastore(s) (e.g., via APIs to third-party data store(s) (e.g., map APIs,menu aggregators, food ordering platforms, search engines, socialnetworks, etc.)), and further embed pointers to such data in theinteractable element 2600. In some examples, such data can be used toprovide an experiential payment processing or ecommerce platform availedvia service(s) of the service provider. While instant applications areused to describe some examples here, such techniques can also beimplemented using lightweight web applications. To target specificrestaurants or merchants, the specific configuration or menus can becustom generated, for example by embedding the merchant's addresslocation, merchant's name, or similar identifier, or identifier of asimilar merchant, to better inform the demonstrative experience.

FIGS. 27A-27G illustrate an example of sharing an instant applicationwith another user, for example as a referral. In one example, a user caninteract with a user interface 2700 that is presented via a merchantcomputing device 2702. In at least one example, the user interface 2700can present a dashboard and can include a selectable element 2704 toenable a merchant to share a referral with another user, such as a newmerchant (e.g., a merchant that is not currently using service(s) of theservice provider). In some examples, techniques described with referenceto FIGS. 27A-27G can use shared data to track and improve the quality ofreferral experience, the conversion success, and discoverability ofservices as described herein.

In at least one example, an interactable element can be generated andcommunicated, in a digital or analog fashion, as described above. Forexample, generation and communication of the interactable element can betriggered via an interaction with the user interface 2700 (e.g., bydetecting a selection of the selectable element 2704). In some examples,the referral can be associated with a payment processing service and/orany other service provided by the service provider, as described herein.In at least one example, based on detecting the selection of theselectable element 2704, an application on the merchant computing device2702 (e.g., a point-of-sale application) can cause another userinterface 2706 to be presented via the merchant computing device 2702.In at least one example, the user interface 2706 can be associated withan instant application that can be sent to another user (e.g., usercomputing device associated therewith). In at least one example, theinstant application can be automatically created/populated, instantlypersonalized with the data associated with the merchant, and can beshared through one or more communication channels. For instance, in atleast one example, based at least in part on detecting selection of aselectable element 2708 associated with the user interface 2706, apop-up, overlay, or other user interface element 2710 can be presentedto enable the merchant to select another user to whom the referral is tobe sent. In at least one example, an interactable element associatedwith the instant application can be associated with a text message,email, push notification or the like. For example, FIG. 27D illustratesan example user interface 2712 associated with an email composition userinterface wherein an interactable element associated with the instantapplication is embedded in an email to be sent to another user. FIG. 27Eillustrates an example user interface 2714 presenting an email asreceived via the user computing device 104 of the other user (e.g., user106). In at least one example, an interactable element associated withthe instant application can be embedded, or otherwise associated withthe email. In some examples, the interactable element can be used totrack when the instant application is shared or forwarded or acted on,using a tracking identifier. In at least one example, an interactableelement can have embedded therein, transaction data, merchant data,location, buyer data, etc., to trigger downloading of an instantapplication that creates a flow for the user 106 before the user 106decides to download the full application, purchase software, or allowpayments for an item, etc. Once the instant application is shared, itcan show up in the sharing medium, e.g., email of the user, as shown inFIG. 27E. In at least one example, the user 106 can select a selectableelement 2716 associated with the user interface 2714 to cause theinstant application to be downloaded on the user computing device 104and/or otherwise initialize the instant application on the usercomputing device 104. FIG. 27F illustrates an example of a userinterface 2718 that can be presented by the instant application to allowthe user 106 to create an account, set up payments, or the like.

In at least one example, user 106 can interact with the instantapplication (e.g., via the user interface 2178) to try one or morefeatures of the application to determine whether they want to downloadthe full application and/or sign-up for a service associated therewith.As illustrated in FIG. 27F, the user interface 2718 can provide detailsassociated with the referral and next steps. In at least one example,the application management component 114 can infer data about the user106 (e.g., based at least in part on input provided via the instantapplication), such as merchant category code (MCC), identityverification data (IDV), third-party data sources, etc. to furthercondense and create a customized and/or personalized experience. Suchdata can also be used to surface one set of functionalities (kitchendisplay system, reservations) to one referral (restaurant) and anotherset (payments, appointments) to a second referral (retail store). Asillustrated by the user interface 2720 in FIG. 27G, the instantapplication can enable the user 106 to perform one or more tasks (e.g.,take payments) without downloading the full application. That is, insome examples, the instant application can enable the recipient toperform one or more tasks via a condensed onboarding flow (e.g.,relative to the onboarding described above with reference to FIG. 27F).In such an example, the user 106 can be taken through a payment tutorialflow or can be instructed to create a new item. If the user 106 desiresto explore further, the full application can be promoted for download.

In some examples, instead of or in addition to a condensed flow, theuser 106 can be presented with a sandbox or a shell of the fullapplication to allow the user 106 to perform a predefined task, such astake payments. The shell too can be made to look like their currentitems, services, and software. In one implementation, since the user 106is a new merchant and the service provider does not have risk data onthe user 106, data associated with the merchant can be used tounderwrite the transactions of the user 106 at least until additionaldata is obtained for the user 106. In such an example, the instantapplication can obtain such approval from the merchant at the time thereferral is created or obtain approval conditions that are to be checkedbefore underwriting the user 106 using the merchant's data. Underwritingtransactions can also be done automatically based on the credit and riskstanding of the merchant and the risk associated with theirtransactions. Accordingly, the user 106 can be provisionally activatedto perform one or more tasks, such as take payments, enable software asa service (SAAS), transfer funds, virtual payments, etc. Based at leastin part on the foregoing, the methods and system can offer at least anacquisition channel that can be customized and/or personalized,experiential, and allows one party to underwrite for another either fora full suite of functionalities or a limited one.

In some examples, the user 106 can explore functionality of theapplication via the user computing device 106 but may want to downloadthe full application on another computing device. In some examples, theuser 106 can request to download the full application via an interactionwith the user interface 2720, via an interaction between the usercomputing device 106 and the other computing device, or the like. In atleast one example, as described above with reference to FIG. 23, theapplication management component 114 can cause the application to bedownloaded on the other computing device. In some examples, data inputvia the user computing device 106 can be stored and transferred to theother computing device. In some examples, such data can be used tocustomized and/or personalize the application and/or data presented viaa user interface associated therewith. In some examples, the userinterface presented via the other computing device can additionally oralternatively be customized and/or personalized based at least in parton device characteristics of the other computing device.

In at least one example, the merchant (e.g., the referee) can receive anotification (e.g., via the merchant computing device 2702) that a newuser has signed up and/or they can receive notification to claim rewardafter the first payment has been made by the new user.

Techniques described herein are examples of techniques that can beimplemented using instant applications. The user interfaces describedabove are illustrative but should not be construed as limiting. That is,additional or alternative user interfaces can be presented via computingdevices, which can include additional or alternative data and/oradditional or alternative configurations.

FIG. 28 illustrates an example environment 2800. The environment 2800includes server computing device(s) 2802 that can communicate overnetwork(s) 2804 with user computing devices 2806 (which, in someexamples can be merchant devices 2808 (individually, 2808(A)-2808(N)))and/or server computing device(s) 2810 associated with third-partyservice provider(s). The server computing device(s) 2802 can beassociated with a service provider 2812 that can provide one or moreservices for the benefit of users 2814, as described below. Actionsattributed to the service provider 2812 can be performed by the servercomputing device(s) 2802. Techniques described above with reference toFIGS. 1-27 can be performed by components of the environment 2800.

In at least one example, the server computing device(s) 2802 cancorrespond to the service provider server(s) 102, the network(s) 2804can correspond to the network(s) 110, and the server computing device(s)2810 can correspond to the third-party server(s) 108 as described abovewith reference to FIG. 1.

The environment 2800 can include a plurality of user computing devices2806, as described above. The user computing device 104 of FIG. 1 cancorrespond to one of the user computing devices of the plurality of usercomputing devices 2806. Each one of the plurality of user computingdevices 2806 can be any type of computing device such as a tabletcomputing device, a smart phone or mobile communication device, alaptop, a netbook or other portable computer or semi-portable computer,a desktop computing device, a terminal computing device or othersemi-stationary or stationary computing device, a dedicated device, awearable computing device or other body-mounted computing device, anaugmented reality device, a virtual reality device, an Internet ofThings (IoT) device, etc. In some examples, individual ones of the usercomputing devices can be operable by users 2814. The users 2814 can bereferred to as customer, buyers, merchants, sellers, borrowers,employees, employers, payors, payees, couriers, and so on. The user 106of FIG. 1 can correspond to any one of the users 2814. The users 2814can interact with the user computing devices 2806 via user interfacespresented via the user computing devices 2806. In at least one example,a user interface can be presented via a web browser, or the like. Inother examples, a user interface can be presented via an application,such as a mobile application or desktop application, which can beprovided by the service provider 2812 or which can be an otherwisededicated application. In some examples, individual of the usercomputing devices 2806 can have an instance or versioned instance of anapplication, which can be downloaded from an application store, forexample, which can present the user interface(s) described herein. Insome examples, a user interface can be presented via a part of anapplication (i.e., an instant application), as described herein. In atleast one example, a user 2814 can interact with the user interface viatouch input, spoken input, or any other type of input.

As described above, in at least one example, the users 2814 can includemerchants 2816 (individually, 2816(A)-2816(N)). In an example, themerchants 2816 can operate respective merchant devices 2808, which canbe user computing devices 2806 configured for use by merchants 2816. Forthe purpose of this discussion, a “merchant” can be any entity thatoffers items (e.g., goods or services) for purchase or other means ofacquisition (e.g., rent, borrow, barter, etc.). The merchants 2816 canoffer items for purchase or other means of acquisition viabrick-and-mortar stores, mobile stores (e.g., pop-up shops, food trucks,etc.), online stores, combinations of the foregoing, and so forth. Insome examples, at least some of the merchants 2816 can be associatedwith a same entity but can have different merchant locations and/or canhave franchise/franchisee relationships. In additional or alternativeexamples, the merchants 2816 can be different merchants. That is, in atleast one example, the merchant 2816(A) is a different merchant than themerchant 2816(B) and/or the merchant 2816(C).

For the purpose of this discussion, “different merchants” can refer totwo or more unrelated merchants. “Different merchants” therefore canrefer to two or more merchants that are different legal entities (e.g.,natural persons and/or corporate persons) that do not share accounting,employees, branding, etc. “Different merchants,” as used herein, havedifferent names, employer identification numbers (EIN)s, lines ofbusiness (in some examples), inventories (or at least portions thereof),and/or the like. Thus, the use of the term “different merchants” doesnot refer to a merchant with various merchant locations orfranchise/franchisee relationships. Such merchants—with various merchantlocations or franchise/franchisee relationships—can be referred to asmerchants having different merchant locations and/or different commercechannels.

Each merchant device 2808 can have an instance of a POS application 2818stored thereon. The POS application 2818 can configure the merchantdevice 2808 as a POS terminal, which enables the merchant 2816(A) tointeract with one or more buyers 2820. As described above, the users2814 can include buyers, such as the buyers 2820 shown as interactingwith the merchant 2816(A). For the purpose of this discussion, a “buyer”can be any entity that acquires items from merchants. While only twobuyers 2820 are illustrated in FIG. 28, any number of buyers 2820 caninteract with the merchants 2816. Further, while FIG. 28 illustrates thebuyers 2820 interacting with the merchant 2816(A), the buyers 2820 caninteract with any of the merchants 2816.

In at least one example, interactions between the buyers 2820 and themerchants 2816 that involve the exchange of funds (from the buyers 2820)for items (from the merchants 2816) can be referred to as“transactions.” In at least one example, the POS application 2818 candetermine transaction data associated with the POS transactions.Transaction data can include payment information, which can be obtainedfrom a reader device 2822 associated with the merchant device 2808(A),user authentication data, purchase amount information, point-of-purchaseinformation (e.g., item(s) purchased, date of purchase, time ofpurchase, etc.), etc. The POS application 2818 can send transaction datato the server computing device(s) 2802. Furthermore, the POS application2818 can present a UI to enable the merchant 2816(A) to interact withthe POS application 2818 and/or the service provider 2812 via the POSapplication 2818.

In at least one example, the merchant device 2808(A) can be aspecial-purpose computing device configured as a POS terminal (via theexecution of the POS application 2818). In at least one example, the POSterminal may be connected to a reader device 2822, which is capable ofaccepting a variety of payment instruments, such as credit cards, debitcards, gift cards, short-range communication based payment instruments,and the like, as described below. In at least one example, the readerdevice 2822 can plug in to a port in the merchant device 2808(A), suchas a microphone port, a headphone port, an audio-jack, a data port, orother suitable port. In additional or alternative examples, the readerdevice 2822 can be coupled to the merchant device 2808(A) via anotherwired or wireless connection, such as via a Bluetooth®, BLE, and so on.Additional details are described below with reference to FIG. 28. Insome examples, the reader device 2822 can read information fromalternative payment instruments including, but not limited to,wristbands and the like.

In some examples, the reader device 2822 may physically interact withpayment instruments such as magnetic stripe payment cards, EMV paymentcards, and/or short-range communication (e.g., near field communication(NFC), radio frequency identification (RFID), Bluetooth®, Bluetooth® lowenergy (BLE), etc.) payment instruments (e.g., cards or devicesconfigured for tapping). The POS terminal may provide a rich userinterface, communicate with the reader device 2822, and communicate withthe server computing device(s) 2802, which can provide, among otherservices, a payment processing platform. The server computing device(s)2802 associated with the service provider 2812 can communicate withserver computing device(s) 2810, as described below. In this manner, thePOS terminal and reader device 2822 may collectively processtransaction(s) between the merchants 2816 (e.g., merchant2816(A)-2816(N)) and buyers 2820 (e.g., buyer 2820(A)-2820(N)). In someexamples, POS terminals and reader devices can be configured inone-to-one pairings. In other examples, the POS terminals and readerdevices can be configured in many-to-one pairings (e.g., one POSterminal coupled to multiple reader devices or multiple POS terminalscoupled to one reader device). In some examples, there could be multiplePOS terminal(s) connected to a number of other devices, such as“secondary” terminals, e.g., back-of-the-house systems, printers,line-buster devices, POS readers, and the like, to allow for informationfrom the secondary terminal to be shared between the primary POSterminal(s) and secondary terminal(s), for example via short-rangecommunication technology. This kind of arrangement may also work in anoffline-online scenario to allow one device (e.g., secondary terminal)to continue taking user input, and synchronize data with another device(e.g., primary terminal) when the primary or secondary terminal switchesto online mode. In other examples, such data synchronization may happenperiodically or at randomly selected time intervals.

While, the POS terminal and the reader device 2822 of the POS system2824 are shown as separate devices, in additional or alternativeexamples, the POS terminal and the reader device 2822 can be part of asingle device. In some examples, the reader device 2822 can have adisplay integrated therein for presenting information to the buyers2820. In additional or alternative examples, the POS terminal can have adisplay integrated therein for presenting information to the buyers2820. POS systems, such as the POS system 2824, may be mobile, such thatPOS terminals and reader devices may process transactions in disparatelocations across the world. POS systems can be used for processingcard-present transactions and card-not-present (CNP) transactions, asdescribed below.

A card-present transaction is a transaction where both a buyer 2820 andhis or her payment instrument are physically present at the time of thetransaction. Card-present transactions may be processed by swipes, dips,taps, or any other interaction between a physical payment instrument(e.g., a card), or otherwise present payment instrument, and a readerdevice 2822 whereby the reader device 2822 is able to obtain paymentdata from the payment instrument. A swipe is a card-present transactionwhere a buyer 2820(A) slides a card, or other payment instrument, havinga magnetic strip through a reader device 2822 that captures payment datacontained in the magnetic strip. A dip is a card-present transactionwhere a buyer 2820(A) inserts a payment instrument having an embeddedmicrochip (i.e., chip) into a reader device 2822 first. The dippedpayment instrument remains in the payment reader until the reader device2822 prompts the buyer 2820(A) to remove the card, or other paymentinstrument. While the payment instrument is in the reader device 2822,the microchip can create a one-time code which is sent from the POSsystem 2824 to the server computing device(s) 2810 (which can beassociated with third-party service providers that provide paymentservices, including but not limited to, an acquirer bank, an issuer,and/or a card payment network (e.g., Mastercard®, VISA®, etc.)) to bematched with an identical one-time code. A tap is a card-presenttransaction where a buyer 2820 may tap or hover his or her paymentinstrument (e.g., card, electronic device such as a smart phone runninga payment application, etc.) over a reader device 2822 to complete atransaction via short-range communication (e.g., NFC, RFID, Bluetooth®,BLE, etc.). Short-range communication enables the payment instrument toexchange information with the reader device 2822. A tap may also becalled a contactless payment.

A CNP transaction is a transaction where a card, or other paymentinstrument, is not physically present at the POS such that payment datais required to be manually keyed in (e.g., by a merchant, buyer, etc.),or payment data is required to be recalled from a card-on-file datastore, to complete the transaction.

In at least one example, a buyer 2820(A) can interact with one of theuser computing devices 2806 (e.g., a buyer device 2826). In at least oneexample, the buyer device 2826 can have an instance of a buyerapplication 2828 installed thereon. In at least one example, the buyerapplication 2828 can present one or more user interfaces to enable thebuyer 2820(A) to send and/or receive funds via a peer-to-peer paymentplatform, as described above. In some examples, as described above, thebuyer application 2828 can exchange communications with the merchantdevice 2808(A) and/or the server computing device(s) 2802 to processcontactless payments. That is, in at least one example, the buyerapplication 2828 can enable the buyer to participate in a peer-to-peertransaction with the merchant via the peer-to-peer payment platform andpayment processing platform described herein.

The POS system 2824, the server computing device(s) 2802, and/or theserver computing device(s) 2810 may exchange payment information andtransaction data to determine whether transactions are authorized. Forexample, the POS system 2824 may provide encrypted payment data, userauthentication data, purchase amount information, point-of-purchaseinformation, etc. (collectively, transaction data) to server computingdevice(s) 2802 over the network(s) 2804. The server computing device(s)2802 may send some of the transaction data, as described above andotherwise described herein, to the server computing device(s) 2810. Asdescribed above, in at least one example, the server computing device(s)2810 can be associated with third-party service providers that providepayment services, including but not limited to, an acquirer bank, anissuer, and/or a card payment network (e.g., Mastercard®, VISA®, etc.)

For the purpose of this discussion, the “payment service providers” canbe acquiring banks (“acquirer”), issuing banks (“issuer”), card paymentnetworks, and the like. In an example, an acquirer is a bank orfinancial institution that processes payments (e.g., credit or debitcard payments) and can assume risk on behalf of merchants(s). Anacquirer can be a registered member of a card association (e.g., Visa®,MasterCard®), and can be part of a card payment network. The acquirer(e.g., the server computing device(s) 2810 associated therewith) cansend a fund transfer request to a server computing device of a cardpayment network (e.g., Mastercard®, VISA®, etc.) to determine whetherthe transaction is authorized or deficient. In at least one example, theservice provider 2812 can serve as an acquirer and connect directly withthe card payment network.

The card payment network (e.g., the server computing device(s) 2810associated therewith) can forward the fund transfer request to anissuing bank (e.g., “issuer”). The issuer is a bank or financialinstitution that offers a financial account (e.g., credit or debit cardaccount) to a user. An issuer can issue payment cards to users and canpay acquirers for purchases made by cardholders to which the issuingbank has issued a payment card. The issuer (e.g., the server computingdevice(s) 2810 associated therewith) can make a determination as towhether the buyer has the capacity to absorb the relevant chargeassociated with the payment transaction. In at least one example, theservice provider 2812 can serve as an issuer and/or can partner with anissuer. The transaction is either approved or rejected by the issuerand/or the card payment network (e.g., the server computing device(s)2810 associated therewith), and a payment authorization message iscommunicated from the issuer to the POS device via a path opposite ofthat described above, or via an alternate path.

As described above, the server computing device(s) 2810, which can beassociated with payment service provider(s), may determine whether thetransaction is authorized based on the transaction data, as well asinformation relating to parties to the transaction (e.g., the buyer 2820and/or the merchant 2816(A)). The server computing device(s) 2810 maysend an authorization notification over the network(s) 2804 to theserver computing device(s) 2802, which may send the authorizationnotification to the POS system 2824 over the network(s) 2804 to indicatewhether the transaction is authorized. The server computing device(s)2802 may also transmit additional information such as transactionidentifiers to the POS system 2824. In one example, the server computingdevice(s) 2802 may include a merchant application and/or otherfunctional components for communicating with the POS system 2824 and/orthe server computing device(s) 2810 to authorize or declinetransactions.

Based on the authorization notification that is received by the POSsystem 2824 from server computing device(s) 2802, the merchant 2816(A)may indicate to the buyer 2820 whether the transaction has beenapproved. In some examples, approval may be indicated at the POS system2824, for example, at a display of the POS system 2824. In otherexamples, such as with a smart phone or watch operating as a short-rangecommunication payment instrument, information about the approvedtransaction may be provided to the short-range communication paymentinstrument for presentation via a display of the smart phone or watch.In some examples, additional or alternative information can additionallybe presented with the approved transaction notification including, butnot limited to, receipts, special offers, coupons, or loyalty programinformation.

As mentioned above, the service provider 2812 can provide, among otherservices, payment processing platforms, inventory management services,catalog management services, business banking services, financingservices, lending services, reservation management services,web-development services, payroll services, employee managementservices, appointment services, loyalty tracking services, restaurantmanagement services, order management services, fulfillment services,peer-to-peer payment services, onboarding services, identityverification (IDV) services, and so on. In some examples, the users 2814can access all of the services of the service provider 2812. In otherexamples, the users 2814 can have gradated access to the services, whichcan be based on risk tolerance, IDV outputs, subscriptions, and so on.In at least one example, access to such services can be availed to themerchants 2816 via the POS application 2818. In additional oralternative examples, each service can be associated with its own accesspoint (e.g., application, web browser, etc.).

The service provider 2812 can offer payment processing platforms forprocessing payments on behalf of the merchants 2816, as described above.For example, the service provider 2812 can provision payment processingsoftware, payment processing hardware and/or payment processingplatforms to merchants 2816, as described above, to enable the merchants2816 to receive payments from the buyers 2820 when conducting POStransactions with the buyers 2820. For instance, the service provider2812 can enable the merchants 2816 to receive cash payments, paymentcard payments, and/or electronic payments from buyers 2820 for POStransactions and the service provider 2812 can process transactions onbehalf of the merchants 2816.

As the service provider 2812 processes transactions on behalf of themerchants 2816, the service provider 2812 can maintain accounts orbalances for the merchants 2816 in one or more ledgers. For example, theservice provider 2812 can analyze transaction data received for atransaction to determine an amount of funds owed to a merchant 2816(A)for the transaction. In at least one example, such an amount can be atotal purchase price less fees charged by the service provider 2812 forproviding the payment processing platforms. Based on determining theamount of funds owed to the merchant 2816(A), the service provider 2812can deposit funds into an account of the merchant 2816(A). The accountcan have a stored balance, which can be managed by the service provider2812. The account can be different from a conventional bank account atleast because the stored balance is managed by a ledger of the serviceprovider 2812 and the associated funds are accessible via variouswithdrawal channels including, but not limited to, scheduled deposit,same-day deposit, instant deposit, and a linked payment instrument.

A scheduled deposit can occur when the service provider 2812 transfersfunds associated with a stored balance of the merchant 2816(A) to a bankaccount of the merchant 2816(A) that is held at a bank or otherfinancial institution (e.g., associated with the server computingdevice(s) 2810). Scheduled deposits can occur at a prearranged timeafter a POS transaction is funded, which can be a business day after thePOS transaction occurred, or sooner or later. In some examples, themerchant 2816(A) can access funds prior to a scheduled deposit. Forinstance, the merchant 2816(A) may have access to same-day deposits(e.g., wherein the service provider 2812 deposits funds from the storedbalance to a linked bank account of the merchant on a same day as POStransaction, in some examples prior to the POS transaction being funded)or instant deposits (e.g., wherein the service provider 2812 depositsfunds from the stored balance to a linked bank account of the merchanton demand, such as responsive to a request). Further, in at least oneexample, the merchant 2816(A) can have a payment instrument that islinked to the stored balance that enables the merchant to access thefunds without first transferring the funds from the account managed bythe service provider 2812 to the bank account of the merchant 2816(A).

In at least one example, the service provider 2812 may provide inventorymanagement services. That is, the service provider 2812 may provideinventory tracking and reporting. Inventory management services mayenable the merchant 2816(A) to access and manage a database storing dataassociated with a quantity of each item that the merchant 2816(A) hasavailable (i.e., an inventory). Furthermore, in at least one example,the service provider 2812 can provide catalog management services toenable the merchant 2816(A) to maintain a catalog, which can be adatabase storing data associated with items that the merchant 2816(A)has available for acquisition (i.e., catalog management services). In atleast one example, the catalog may include a plurality of data items anda data item of the plurality of data items may represent an item thatthe merchant 2861(A) has available for acquisition. The service provider2812 can offer recommendations related to pricing of the items,placement of items on the catalog, and multi-party fulfilment of theinventory.

In at least one example, the service provider 2812 can provide businessbanking services, which allow the merchant 2816(A) to track deposits(from payment processing and/or other sources of funds) into an accountof the merchant 2816(A), payroll payments from the account (e.g.,payments to employees of the merchant 2816(A)), payments to othermerchants (e.g., business-to-business) directly from the account or froma linked debit card, withdrawals made via scheduled deposit and/orinstant deposit, etc. Furthermore, the business banking services canenable the merchant 2816(A) to obtain a customized payment instrument(e.g., credit card), check how much money they are earning (e.g., viapresentation of available earned balance), understand where their moneyis going (e.g., via deposit reports (which can include a breakdown offees), spend reports, etc.), access/use earned money (e.g., viascheduled deposit, instant deposit, linked payment instrument, etc.),feel in control of their money (e.g., via management of depositschedule, deposit speed, linked instruments, etc.), etc. Moreover, thebusiness banking services can enable the merchants 2816 to visualizetheir cash flow to track their financial health, set aside money forupcoming obligations (e.g., savings), organize money around goals, etc.

In at least one example, the service provider 2812 can provide financingservices and products, such as via business loans, consumer loans, fixedterm loans, flexible term loans, and the like. In at least one example,the service provider 2812 can utilize one or more risk signals todetermine whether to extend financing offers and/or terms associatedwith such financing offers.

In at least one example, the service provider 2812 can provide financingservices for offering and/or lending a loan to a borrower that is to beused for, in some instances, financing the borrower's short-termoperational needs (e.g., a capital loan). For instance, a potentialborrower that is a merchant can obtain a capital loan via a capital loanproduct in order to finance various operational costs (e.g., rent,payroll, inventory, etc.). In at least one example, the service provider2812 can offer different types of capital loan products. For instance,in at least one example, the service provider 2812 can offer a dailyrepayment loan product, wherein a capital loan is repaid daily, forinstance, from a portion of transactions processed by the paymentprocessing platform on behalf of the borrower. Additionally and/oralternatively, the service provider 2812 can offer a monthly repaymentloan product, wherein a capital loan is repaid monthly, for instance,via a debit from a bank account linked to the payment processingplatform. The credit risk of the merchant may be evaluated using riskmodels that take into account factors, such as payment volume, creditrisk of similarly situated merchants, past transaction history,seasonality, credit history, and so on.

Additionally or alternatively, the service provider 2812 can providefinancing services for offering and/or lending a loan to a borrower thatis to be used for, in some instances, financing the borrower's consumerpurchase (e.g., a consumer loan). In at least one example, a borrowercan submit a request for a loan to enable the borrower to purchase anitem from a merchant, which can be one of the merchants 2816. Theservice provider 2812 can generate the loan based at least in part ondetermining that the borrower purchased or intends to purchase the itemfrom the merchant. The loan can be associated with a balance based on anactual purchase price of the item and the borrower can repay the loanover time. In some examples, the borrower can repay the loan viainstallments, which can be paid via funds managed and/or maintained bythe service provider 2812 (e.g., from payments owed to the merchant frompayments processed on behalf of the merchant, funds transferred to themerchant, etc.). The service provider 2812 can offer specific financialproducts, such as payment instruments, tied specifically to the loanproducts. For example, in one implementation, the service provider 2812associates capital to a merchant or buyer's debit card, where the use ofthe debit card is defined by the terms of the loan. In some examples,the merchant may only use the debit card for making specific purchases.In other examples, the “installment” associated with the loan product iscredited directly via the payment instrument. The payment instrument isthus customized to the loan and/or the parties associated with the loan.

The service provider 2812 can provide web-development services, whichenable users 2814 who are unfamiliar with HTML, XML, Javascript, CSS, orother web design tools to create and maintain professional andaesthetically pleasing websites. Some of these web page editingapplications allow users to build a web page and/or modify a web page(e.g., change, add, or remove content associated with a web page).Further, in addition to websites, the web-development services cancreate and maintain other online omni-channel presences, such as socialmedia posts for example. In some examples, the resulting web page(s)and/or other content items can be used for offering item(s) for sale viaan online/e-commerce platform. That is, the resulting web page(s) and/orother content items can be associated with an online store or offeringby the one or more of the merchants 2816. In at least one example, theservice provider 2812 can recommend and/or generate content items tosupplement omni-channel presences of the merchants 2816. That is, if amerchant of the merchants 2816 has a web page, the service provider2812—via the web-development or other services—can recommend and/orgenerate additional content items to be presented via other channel(s),such as social media, email, etc.

Furthermore, the service provider 2812 can provide payroll services toenable employers to pay employees for work performed on behalf ofemployers. In at least one example, the service provider 2812 canreceive data that includes time worked by an employee (e.g., throughimported timecards and/or POS interactions), sales made by the employee,gratuities received by the employee, and so forth. Based on such data,the service provider 2812 can make payroll payments to employee(s) onbehalf of an employer via the payroll service. For instance, the serviceprovider 2812 can facilitate the transfer of a total amount to be paidout for the payroll of an employee from the bank of the employer to thebank of the service provider 2812 to be used to make payroll payments.In at least one example, when the funds have been received at the bankof the service provider 2812, the service provider 2812 can pay theemployee, such as by check or direct deposit, often a day, a week, ormore after when the work was actually performed by the employee. Inadditional or alternative examples, the service provider 2812 can enableemployee(s) to receive payments via same-day or instant deposit based atleast in part on risk and/or reliability analyses performed by theservice provider 2812.

Moreover, in at least one example, the service provider 2812 can provideemployee management services for managing schedules of employees.Further, the service provider 2812 can provide appointment services forenabling users 2814 to set schedules for scheduling appointments and/orusers 2814 to schedule appointments.

In some examples, the service provider 2812 can provide restaurantmanagement services to enable users 2814 to make and/or managereservations, to monitor front-of-house and/or back-of-house operations,and so on. In such examples, the merchant device(s) 2808 and/or servercomputing device(s) 2802 can be configured to communicate with one ormore other computing devices, which can be located in the front-of-house(e.g., POS device(s)) and/or back-of-house (e.g., kitchen displaysystem(s) (KDS)). In at least one example, the service provider 2812 canprovide order management services and/or fulfillment services to enablerestaurants to manage open tickets, split tickets, and so on and/ormanage fulfillment services. In some examples, such services can beassociated with restaurant merchants, as described above. In additionalor alternative examples, such services can be any type of merchant.

In at least one example, the service provider 2812 can providefulfilment services, which can use couriers for delivery, whereincouriers can travel between multiple locations to provide deliveryservices, photography services, etc. Couriers can be users 2814 who cantravel between locations to perform services for a requesting user 2814(e.g., deliver items, capture images, etc.). In some examples, thecourier can receive compensation from the service provider 2812. Thecourier can employ one or more vehicles, such as automobiles, bicycles,scooters, motorcycles, buses, airplanes, helicopters, boats,skateboards, etc. Although, in other instances the courier can travel byfoot or otherwise without a vehicle. Some examples discussed hereinenable people to participate as couriers in a type of crowdsourcedservice economy. Here, essentially any person with a mobile device isable to immediately become a courier, or cease to be a courier, in acourier network that provides services as described herein. In at leastone example, the couriers can be unmanned aerial vehicles (e.g.,drones), autonomous vehicles, or any other type of vehicle capable ofreceiving instructions for traveling between locations. In someexamples, the service provider 2812 can receive requests for courierservices, automatically assign the requests to active couriers, andcommunicate dispatch instructions to couriers via user interface (e.g.,application, web browser, or other access point) presented viarespective devices 2806.

In some examples, the service provider 2812 can provide omni-channelfulfillment services. For instance, if a buyer places an order with amerchant and the merchant cannot fulfill the order because one or moreitems are out of stock or otherwise unavailable, the service provider2812 can leverage other merchants and/or sales channels that are part ofthe platform of the service provider 2812 to fulfill the buyer's order.That is, another merchant can provide the one or more items to fulfillthe order of the buyer. Furthermore, in some examples, another saleschannel (e.g., online, brick-and-mortar, etc.) can be used to fulfillthe order of the buyer.

In some examples, the service provider 2812 can enable conversationalcommerce via conversational commerce services, which can use one or moremachine learning mechanisms to analyze messages exchanged between two ormore users 2814, voice inputs into a virtual assistant or the like, todetermine intents of user(s) 2814. In some examples, the serviceprovider 2812 can utilize determined intents to automate buyer service,offer promotions, provide recommendations, or otherwise interact withbuyers in real-time. In at least one example, the service provider 2812can integrate products and services, and payment mechanisms into acommunication platform (e.g., messaging, etc.) to enable buyers to makepurchases, or otherwise transact, without having to call, email, orvisit a web page or other channel of a merchant. That is, conversationalcommerce alleviates the need for buyers to toggle back and forth betweenconversations and web pages to gather information and make purchases.

In at least one example, the service provider 2812 (e.g., the servercomputing device(s) 2802) can provide a peer-to-peer payment service,via a peer-to-peer payment platform as described herein, that enablespeer-to-peer payments between two or more users 2814. In at least oneexample, the service provider 2812 can communicate with instances of apayment application (or other access points) installed on devices 2806configured for operation by users, such as the buyers 2820(A)-2820(N).An example of such a payment application is the buyer application 2828described above, which can be installed on a buyer device 2826. In anexample, an instance of the payment application executing on a firstdevice operated by a payor can send a request to the service provider2812 to transfer an amount of funds (e.g., fiat currency or non-fiatcurrency such as cryptocurrency, securities, and related assets) from anaccount of the payor to an account of a payee (e.g., a peer-to-peerpayment). In at least one example, the buyer 2820(A) can be a payorand/or a payee (i.e., a user) and the payment processing platformdescribed herein can be a payor and/or a payee on behalf of one or moremerchants. The service provider 2812 can facilitate the transfer and cansend a notification to an instance of the payment application executingon a second mobile device operated by the payee that the transfer is inprocess (or has been completed). In some examples, the service provider2812 can send additional or alternative information to the instances ofthe payment application (e.g., low balance to the payor, current balanceto the payor or the payee, etc.). In some implementations, the payorand/or payee can be identified automatically, e.g., based on context,proximity, prior transaction history, and so on. In other examples, thepayee can send a request for funds to the payor prior to the payorinitiating the transfer of funds. The funds transferred can beassociated with any digital currency type, including, but not limitedto, cash, cryptocurrency, etc. In some embodiments, the service provider2812 funds the request to payee on behalf of the payor, to speed up thetransfer process and compensate for any lags that may be attributed topayor's financial network.

In some implementations, the service provider 2812 can trigger thepeer-to-peer payment process through identification of a “payment proxy”having a particular syntax. For example, the syntax includes a monetarycurrency indicator prefixing one or more alphanumeric characters (e.g.,$Cash). The currency indicator operates as the tagging mechanism thatindicates to a computer system to treat the inputs as a request from thesender to transfer cash, where detection of the syntax (which includesone or more alphanumeric characters tagged by a monetary currencyindicator) triggers a transfer of cash. The currency indicator cancorrespond to various currencies including but not limited to, dollar($), euro (€), pound (£), rupee (

), yuan (¥), etc. Although use of the dollar currency indicator ($) isused herein, it is to be understood that any currency symbol couldequally be used. The peer-to-peer process can be initiated through aparticular application executing on the user computing devices 2806(e.g., the buyer application 2828).

In some embodiments, the peer-to-peer process can be implemented withina forum context. The term “forum,” as used here, refers to a contentprovider's media channel (e.g., a social networking platform, amicroblog, a blog, video sharing platform, a music sharing platform,etc.) that enables user interaction and engagement through comments,posts, messages on electronic bulletin boards, messages on a socialnetworking platform, and/or any other types of messages. The forum canbe employed by a content provider to enable users of the forum tointeract with one another, (e.g., through creating messages, postingcomments, etc.). In some embodiments, “forum” may also refer to anapplication or webpage of an e-commerce or retail organization thatoffers products and/or services. Such websites can provide an online“form” to complete before or after the products or services are added toa virtual cart. The online form may include one or more fields toreceive user interaction and engagement. Examples include name and otheridentification of the user, shipping address of the user, etc. Some ofthese fields may be configured to receive payment information, such as apayment proxy, in lieu of other kinds of payment mechanisms, such ascredit cards, debit cards, prepaid cards, gift cards, virtual wallets,etc.

In some embodiments, the peer-to-peer process can be implemented withina communication application context, such as a messaging applicationcontext. The term “messaging application,” as used here, refers to anymessaging application that enables communication between users (e.g.,sender and recipient of a message) over a wired or wirelesscommunications network, through use of a communication message. Themessaging application can be employed by the service provider 2812. Forinstance, the service provider 2812 can offer messaging services thatprovides a communication service to users via a messaging application(e.g., chat or messaging capability). The messaging application caninclude, for example, a text messaging application for communicationbetween phones (e.g., conventional mobile telephones or smartphones), ora cross-platform instant messaging application for smartphones andphones that use the Internet for communication. The messagingapplication can be executed on a user computing device 2806 (e.g.,mobile device or conventional personal computer (PC)) based oninstructions transmitted to and from the server computing device(s) 2802(which, in such an example can be called a “messaging server”). In someinstances, the messaging application can include a payment applicationwith messaging capability that enables users of the payment applicationto communicate with one another. In such instances, the paymentapplication can be executed on the user computing device 2806 based oninstructions transmitted to and from the server computing device(s) 2802(e.g., the payment service discussed in this description or anotherpayment service that supports payment transactions).

In at least some embodiments, the peer-to-peer process can beimplemented within a landing page context. The term “landing page,” asused here, refers to a virtual location identified by a personalizedlocation address that is dedicated to collect payments on behalf of arecipient associated with the personalized location address. Thepersonalized location address that identifies the landing page caninclude a payment proxy discussed above. The service provider 2812 cangenerate the landing page to enable the recipient to convenientlyreceive one or more payments from one or more senders. In someembodiments, the personalized location address identifying the landingpage is a uniform resource locator (URL) that incorporates the paymentproxy. In such embodiments, the landing page is a web page, e.g.,www.cash.me/$Cash.

In at least one example, a user 2816(A) may be new to the serviceprovider 2812 such that the user 2816(A) that has not registered (e.g.,subscribed to receive access to one or more services offered by theservice provider) with the service provider 2812. The service provider2812 can offer onboarding services for registering a potential user2816(A) with the service provider 2812. In some examples, onboarding caninvolve presenting various questions, prompts, and the like to apotential user 2816(A) to obtain information that can be used togenerate a profile for the potential user 2816(A). In at least oneexample, the service provider 2812 can provide limited or short-termaccess to its services prior to, or during, onboarding (e.g., a user ofa peer-to-peer payment service can transfer and/or receive funds priorto being fully onboarded, a merchant can process payments prior to beingfully onboarded, etc.). In at least one example, responsive to thepotential user 2816(A) providing all necessary information, thepotential user 2816(A) can be onboarded to the service provider 2812. Insuch an example, any limited or short-term access to services of theservice provider 2812 can be transitioned to more permissive (e.g., lesslimited) or longer-term access to such services.

The service provider 2812 can be associated with IDV services, which canbe used by the service provider 2812 for compliance purposes and/or canbe offered as a service, for instance to third-party service providers(e.g., associated with the server computing device(s) 2810). That is,the service provider 2812 can offer IDV services to verify the identityof users 2814 seeking to use or using their services. Identityverification requires a buyer (or potential buyer) to provideinformation that is used by compliance departments to prove that theinformation is associated with an identity of a real person or entity.In at least one example, the service provider 2812 can perform servicesfor determining whether identifying information provided by a user 2814accurately identifies the buyer (or potential buyer) (i.e., Is the buyerwho they say they are?).

The service provider 2812 is capable of providing additional oralternative services and the services described above are offered as asampling of services. In at least one example, the service provider 2812can exchange data with the server computing device(s) 2810 associatedwith third-party service providers. Such third-party service providerscan provide information that enables the service provider 2812 toprovide services, such as those described above. In additional oralternative examples, such third-party service providers can accessservices of the service provider 2812. That is, in some examples, thethird-party service providers can be subscribers, or otherwise access,services of the service provider 2812.

Techniques described herein can be configured to operate in bothreal-time/online and offline modes. “Online” modes refer to modes whendevices are capable of communicating with the service provider 2812(e.g., the server computing device(s) 2802) and/or the server computingdevice(s) 2810 via the network(s) 2804. In some examples, the merchantdevice(s) 2808 are not capable of connecting with the service provider2812 (e.g., the server computing device(s) 2802) and/or the servercomputing device(s) 2810, due to a network connectivity issue, forexample. In additional or alternative examples, the server computingdevice(s) 2802 are not capable of communicating with the servercomputing device(s) 2810 due to network connectivity issue, for example.In such examples, devices may operate in “offline” mode where at leastsome payment data is stored (e.g., on the merchant device(s) 2808)and/or the server computing device(s) 2802 until connectivity isrestored and the payment data can be transmitted to the server computingdevice(s) 2802 and/or the server computing device(s) 2810 forprocessing.

In at least one example, the service provider 2812 can be associatedwith a hub, such as an order hub, an inventory hub, a fulfillment huband so on, which can enable integration with one or more additionalservice providers (e.g., associated with the additional server computingdevice(s) 2810). In some examples, such additional service providers canoffer additional or alternative services and the service provider 2812can provide an interface or other computer-readable instructions tointegrate functionality of the service provider 2812 into the one ormore additional service providers.

Techniques described herein are directed to services provided via adistributed system of user computing devices 2806 that are incommunication with one or more server computing devices 2802 of theservice provider 2812. That is, techniques described herein are directedto a specific implementation—or, a practical application—of utilizing adistributed system of user computing devices 2806 that are incommunication with one or more server computing devices 2802 of theservice provider 2812 to perform a variety of services, as describedabove. The unconventional configuration of the distributed systemdescribed herein enables the server computing device(s) 2802 that areremotely-located from end-users (e.g., users 2814) to intelligentlyoffer services based on aggregated data associated with the end-users,such as the users 2814 (e.g., data associated with multiple, differentmerchants and/or multiple, different buyers), in some examples, innear-real time. Accordingly, techniques described herein are directed toa particular arrangement of elements that offer technical improvementsover conventional techniques for performing payment processing platformsand the like. For small business owners in particular, the businessenvironment is typically fragmented and relies on unrelated tools andprograms, making it difficult for an owner to manually consolidate andview such data. The techniques described herein constantly orperiodically monitor disparate and distinct merchant accounts, e.g.,accounts within the control of the service provider 2812, and thoseoutside of the control of the service provider 2812, to track thebusiness standing (payables, receivables, payroll, invoices,appointments, capital, etc.) of the merchants. The techniques hereinprovide a consolidated view of a merchant's cash flow, predict needs,preemptively offer recommendations or services, such as capital,coupons, etc., and/or enable money movement between disparate accounts(merchant's, another merchant's, or even payment service's) in africtionless and transparent manner.

As described herein, artificial intelligence, machine learning, and thelike can be used to dynamically make determinations, recommendations,and the like, thereby adding intelligence and context-awareness to anotherwise one-size-fits-all scheme for providing payment processingplatforms and/or additional or alternative services described herein. Insome implementations, the distributed system is capable of applying theintelligence derived from an existing user base to a new user, therebymaking the onboarding experience for the new user personalized andfrictionless when compared to traditional onboarding methods. Thus,techniques described herein improve existing technological processes.

As described above, various graphical user interfaces (GUIs) can bepresented to facilitate techniques described herein. Some of thetechniques described herein are directed to user interface featurespresented via GUIs to improve interaction between users 2814 and usercomputing devices 2806. Furthermore, such features are changeddynamically based on the profiles of the users involved interacting withthe GUIs. As such, techniques described herein are directed toimprovements to computing systems.

FIG. 29 depicts an illustrative block diagram illustrating a system 2900for performing techniques described herein. The system 2900 includes auser computing device 2902, that communicates with server computingdevice(s) (e.g., server(s) 2904) via network(s) 2906 (e.g., theInternet, cable network(s), cellular network(s), cloud network(s),wireless network(s) (e.g., Wi-Fi) and wired network(s), as well asclose-range communications such as Bluetooth®, Bluetooth® low energy(BLE), and the like). While a single user computing device 2902 isillustrated, in additional or alternate examples, the system 2900 canhave multiple user computing devices, as described above with referenceto FIG. 25.

In at least one example, the user computing device 2902 can correspondto the user computing device 104, the server(s) 2904 can correspond tothe service provider server(s) 102, and the network(s) 2906 cancorrespond to the network(s) 110 as described above with reference toFIG. 1.

In at least one example, the user computing device 2902 can be anysuitable type of computing device, e.g., portable, semi-portable,semi-stationary, or stationary. Some examples of the user computingdevice 2902 can include, but are not limited to, a tablet computingdevice, a smart phone or mobile communication device, a laptop, anetbook or other portable computer or semi-portable computer, a desktopcomputing device, a terminal computing device or other semi-stationaryor stationary computing device, a dedicated device, a wearable computingdevice or other body-mounted computing device, an augmented realitydevice, a virtual reality device, an Internet of Things (IoT) device,etc. That is, the user computing device 2902 can be any computing devicecapable of sending communications and performing the functions accordingto the techniques described herein. The user computing device 2902 caninclude devices, e.g., payment card readers, or components capable ofaccepting payments, as described below.

In the illustrated example, the user computing device 2902 includes oneor more processors 2908, one or more computer-readable media 2910, oneor more communication interface(s) 2912, one or more input/output (I/O)devices 2914, a display 2916, and sensor(s) 2918.

In at least one example, each processor 2908 can itself comprise one ormore processors or processing cores. For example, the processor(s) 2908can be implemented as one or more microprocessors, microcomputers,microcontrollers, digital signal processors, central processing units,state machines, logic circuitries, and/or any devices that manipulatesignals based on operational instructions. In some examples, theprocessor(s) 2908 can be one or more hardware processors and/or logiccircuits of any suitable type specifically programmed or configured toexecute the algorithms and processes described herein. The processor(s)2908 can be configured to fetch and execute computer-readableprocessor-executable instructions stored in the computer-readable media2910.

Depending on the configuration of the user computing device 2902, thecomputer-readable media 2910 can be an example of tangiblenon-transitory computer storage media and can include volatile andnonvolatile memory and/or removable and non-removable media implementedin any type of technology for storage of data such as computer-readableprocessor-executable instructions, data structures, program modules orother data. The computer-readable media 2910 can include, but is notlimited to, RAM, ROM, EEPROM, flash memory, solid-state storage,magnetic disk storage, optical storage, and/or other computer-readablemedia technology. Further, in some examples, the user computing device2902 can access external storage, such as RAID storage systems, storagearrays, network attached storage, storage area networks, cloud storage,or any other medium that can be used to store data and that can beaccessed by the processor(s) 2908 directly or through another computingdevice or network. Accordingly, the computer-readable media 2910 can becomputer storage media able to store instructions, modules or componentsthat can be executed by the processor(s) 2908. Further, when mentioned,non-transitory computer-readable media exclude media such as energy,carrier signals, electromagnetic waves, and signals per se.

The computer-readable media 2910 can be used to store and maintain anynumber of functional components that are executable by the processor(s)2908. In some implementations, these functional components compriseinstructions or programs that are executable by the processor(s) 2908and that, when executed, implement operational logic for performing theactions and services attributed above to the user computing device 2902.Functional components stored in the computer-readable media 2910 canenable a user interface 2920 to be presented so that users can interactwith the user computing device 2902, and thus the server(s) 2904 and/orother networked devices. In at least one example, the user interface2920 can be presented via a web browser, or the like. In other examples,the user interface 2920 can be presented via an application, such as amobile application or desktop application, which can be provided by aservice provider 412 associated with the server(s) 2904, or which can bean otherwise dedicated application. In some examples, the user interface2920 can be presented via an instant application, as described above. Inat least one example, a user can interact with the user interface viatouch input, spoken input, gesture, or any other type of input. The word“input” is also used to describe “contextual” input that may not bedirectly provided by the user via the user interface 2920. For example,user's interactions with the user interface 2920 are analyzed using,e.g., natural language processing techniques, to determine context orintent of the user, which may be treated in a manner similar to “direct”user input.

Depending on the type of the user computing device 2902, thecomputer-readable media 2910 can also optionally include otherfunctional components and data, such as other modules and data 2922,which can include programs, drivers, etc., and the data used orgenerated by the functional components. In addition, thecomputer-readable media 2910 can also store data, data structures andthe like, that are used by the functional components. Further, the usercomputing device 2902 can include many other logical, programmatic andphysical components, of which those described are merely examples thatare related to the discussion herein.

In at least one example, the computer-readable media 2910 can includeadditional functional components, such as an operating system 2924 forcontrolling and managing various functions of the user computing device2902 and for enabling basic user interactions.

The communication interface(s) 2912 can include one or more interfacesand hardware components for enabling communication with various otherdevices, such as over the network(s) 2906 or directly. For example,communication interface(s) 2912 can enable communication through one ormore network(s) 2906, which can include, but are not limited any type ofnetwork known in the art, such as a local area network or a wide areanetwork, such as the Internet, and can include a wireless network, suchas a cellular network, a cloud network, a local wireless network, suchas Wi-Fi and/or close-range wireless communications, such as Bluetooth®,BLE, NFC, RFID, a wired network, or any other such network, or anycombination thereof. Accordingly, network(s) 2906 can include both wiredand/or wireless communication technologies, including Bluetooth®, BLE,Wi-Fi and cellular communication technologies, as well as wired or fiberoptic technologies. Components used for such communications can dependat least in part upon the type of network, the environment selected, orboth. Protocols for communicating over such networks are well known andwill not be discussed herein in detail.

Embodiments of the disclosure may be provided to users through a cloudcomputing infrastructure. Cloud computing refers to the provision ofscalable computing resources as a service over a network, to enableconvenient, on-demand network access to a shared pool of configurablecomputing resources that can be rapidly provisioned and released withminimal management effort or service provider interaction. Thus, cloudcomputing allows a user to access virtual computing resources (e.g.,storage, data, applications, and even complete virtualized computingsystems) in “the cloud,” without regard for the underlying physicalsystems (or locations of those systems) used to provide the computingresources.

The user computing device 2902 can further include one or moreinput/output (I/O) devices 2914. The I/O devices 2914 can includespeakers, a microphone, a camera, and various user controls (e.g.,buttons, a joystick, a keyboard, a keypad, etc.), a haptic outputdevice, and so forth. The I/O devices 2914 can also include attachmentsthat leverage the accessories (audio-jack, USB-C, Bluetooth, etc.) toconnect with the user computing device 2902.

In at least one example, user computing device 2902 can include adisplay 2916. Depending on the type of computing device(s) used as theuser computing device 2902, the display 2916 can employ any suitabledisplay technology. For example, the display 2916 can be a liquidcrystal display, a plasma display, a light emitting diode display, anOLED (organic light-emitting diode) display, an electronic paperdisplay, or any other suitable type of display able to present digitalcontent thereon. In at least one example, the display 2916 can be anaugmented reality display, a virtually reality display, or any otherdisplay able to present and/or project digital content. In someexamples, the display 2916 can have a touch sensor associated with thedisplay 2916 to provide a touchscreen display configured to receivetouch inputs for enabling interaction with a graphic interface presentedon the display 2916. Accordingly, implementations herein are not limitedto any particular display technology. Alternatively, in some examples,the user computing device 2902 may not include the display 2916, anddata can be presented by other means, such as aurally, hapticly, etc.

In addition, the user computing device 2902 can include sensor(s) 2918.The sensor(s) 2918 can include a GPS device able to indicate locationdata. Further, the sensor(s) 2918 can include, but are not limited to,an accelerometer, gyroscope, compass, proximity sensor, camera,microphone, and/or a switch.

In some examples, the GPS device can be used to identify a location of auser. In at least one example, the location of the user can be used bythe service provider 2812, described above, to provide one or moreservices. That is, in some examples, the service provider 2812 canimplement geofencing to provide particular services to users. As anexample, with a lending service, location can be used to confirm that astated purpose of a loan corresponds to evidence of use (e.g., Is theuser using the loan consistent with what he or she said he or she wasgoing to use it for?). Furthermore, in some examples, location can beused for payroll purposes. As an example, if a contractor completes aproject, the contractor can provide a geo-tagged image (e.g., taggedbased on location data availed by the GPS device). In some examples,location can be used for facilitating peer-to-peer payments betweennearby users and/or for sending users notifications regarding availableappointments with merchant(s) located proximate to the users. In atleast one example, location can be used for taking payments from nearbybuyers when they leave a geofence, or location can be used to initiatean action responsive to users entering a brick-and-mortar store of amerchant. Location can be used in additional or alternative ways aswell.

Additionally, the user computing device 2902 can include various othercomponents that are not shown, examples of which include removablestorage, a power source, such as a battery and power control unit, abarcode scanner, a printer, a cash drawer, and so forth.

In addition, in some examples, the user computing device 2902 caninclude, be connectable to, or otherwise be coupled to a reader device2926, for reading payment instruments and/or identifiers associated withother objects. In some examples, as described above, the reader device2926 can plug in to a port in the user computing device 2902, such as amicrophone port, a headphone port, an audio-jack, a data port, or othersuitable port. In additional or alternative examples, the reader device2926 can be coupled to the user computing device 2902 via another wiredor wireless connection, such as via a Bluetooth®, BLE, and so on. Thereader device 2926 can include a read head for reading a magnetic stripof a payment card, and further can include encryption technology forencrypting the data read from the magnetic strip. Additionally oralternatively, the reader device 2926 can be an EMV payment reader,which in some examples, can be embedded in the user computing device2902. Moreover, numerous other types of readers can be employed with theuser computing device 2902 herein, depending on the type andconfiguration of the user computing device 2902.

The reader device 2926 may be a portable magnetic stripe card reader,optical scanner, smartcard (card with an embedded IC chip) reader (e.g.,an EMV-compliant card reader or short-range communication-enabledreader), RFID reader, or the like, configured to detect and obtain dataoff any payment instrument. Accordingly, the reader device 2926 mayinclude hardware implementation, such as slots, magnetic tracks, andrails with one or more sensors or electrical contacts to facilitatedetection and acceptance of a payment instrument. That is, the readerdevice 2926 may include hardware implementations to enable the readerdevice 2926 to interact with a payment instrument via a swipe (i.e., acard-present transaction where a buyer slides a card having a magneticstrip through a payment reader that captures payment data contained inthe magnetic strip), a dip (i.e., a card-present transaction where abuyer inserts a card having an embedded microchip (i.e., chip) into apayment reader first until the payment reader prompts the buyer toremove the card), or a tap (i.e., a card-present transaction where abuyer may tap or hover his or her electronic device such as a smartphone running a payment application over a payment reader to complete atransaction via short-range communication) to obtain payment dataassociated with a buyer. Additionally or optionally, the reader device2926 may also include a biometric sensor to receive and processbiometric characteristics and process them as payment instruments, giventhat such biometric characteristics are registered with the serviceprovider and connected to a financial account with a bank server.

The reader device 2926 may include processing unit(s), computer-readablemedia, a reader chip, a transaction chip, a timer, a clock, a networkinterface, a power supply, and so on. The processing unit(s) of thereader device 2926 may execute one or more modules and/or processes tocause the reader device 2926 to perform a variety of functions, as setforth above and explained in further detail in the following disclosure.In some examples, the processing unit(s) may include a centralprocessing unit (CPU), a graphics processing unit (GPU), a CPU and aGPU, or processing units or components known in the art. Additionally,each of the processing unit(s) may possess its own local memory, whichalso may store program modules, program data, and/or one or moreoperating systems. Depending on the exact configuration and type of thereader device 2926, the computer-readable media may include volatilememory (such as RAM), non-volatile memory (such as ROM, flash memory,miniature hard drive, memory card, or the like), or some combinationthereof. In at least one example, the computer-readable media of thereader device 2926 may include at least one module for performingvarious functions as described herein.

The reader chip may perform functionalities to control the operationsand processing of the reader device 2926. That is, the reader chip mayperform functionalities to control payment interfaces (e.g., acontactless interface, a contact interface, etc.), a wirelesscommunication interface, a wired interface, a user interface (e.g., asignal condition device (FPGA)), etc. Additionally, the reader chip mayperform functionality to control the timer, which may provide a timersignal indicating an amount of time that has lapsed following aparticular event (e.g., an interaction, a power-down event, etc.).Moreover, the reader chip may perform functionality to control the clock296, which may provide a clock signal indicating a time. Furthermore,the reader chip may perform functionality to control the networkinterface, which may interface with the network(s) 2906, as describedbelow.

Additionally, the reader chip may perform functionality to control thepower supply. The power supply may include one or more power suppliessuch as a physical connection to AC power or a battery. Power supply mayinclude power conversion circuitry for converting AC power andgenerating a plurality of DC voltages for use by components of readerdevice 2926. When power supply includes a battery, the battery may becharged via a physical power connection, via inductive charging, or viaany other suitable method.

The transaction chip may perform functionalities relating to processingof payment transactions, interfacing with payment instruments,cryptography, and other payment-specific functionality. That is, thetransaction chip may access payment data associated with a paymentinstrument and may provide the payment data to a POS terminal, asdescribed above. The payment data may include, but is not limited to, aname of the buyer, an address of the buyer, a type (e.g., credit, debit,etc.) of a payment instrument, a number associated with the paymentinstrument, a verification value (e.g., PIN Verification Key Indicator(PVKI), PIN Verification Value (PVV), Card Verification Value (CVV),Card Verification Code (CVC), etc.) associated with the paymentinstrument, an expiration data associated with the payment instrument, aprimary account number (PAN) corresponding to the buyer (which may ormay not match the number associated with the payment instrument),restrictions on what types of charges/debts may be made, etc.Additionally, the transaction chip may encrypt the payment data uponreceiving the payment data.

It should be understood that in some examples, the reader chip may haveits own processing unit(s) and computer-readable media and/or thetransaction chip may have its own processing unit(s) andcomputer-readable media. In other examples, the functionalities ofreader chip and transaction chip may be embodied in a single chip or aplurality of chips, each including any suitable combination ofprocessing units and computer-readable media to collectively perform thefunctionalities of reader chip and transaction chip as described herein.

While, the user computing device 2902, which can be a POS terminal, andthe reader device 2926 are shown as separate devices, in additional oralternative examples, the user computing device 2902 and the readerdevice 2926 can be part of a single device, which may be abattery-operated device. In such an example, components of both the usercomputing device 2902 and the reader device 2926 may be associated withthe single device. In some examples, the reader device 2926 can have adisplay integrated therewith, which can be in addition to (or as analternative of) the display 2916 associated with the user computingdevice 2902.

The server(s) 2904 can include one or more servers or other types ofcomputing devices that can be embodied in any number of ways. Forexample, in the example of a server, the modules, other functionalcomponents, and data can be implemented on a single server, a cluster ofservers, a server farm or data center, a cloud-hosted computing service,a cloud-hosted storage service, and so forth, although other computerarchitectures can additionally or alternatively be used.

Further, while the figures illustrate the components and data of theserver(s) 2904 as being present in a single location, these componentsand data can alternatively be distributed across different computingdevices and different locations in any manner. Consequently, thefunctions can be implemented by one or more server computing devices,with the various functionality described above distributed in variousways across the different computing devices. Multiple server(s) 2904 canbe located together or separately, and organized, for example, asvirtual servers, server banks and/or server farms. The describedfunctionality can be provided by the servers of a single merchant orenterprise, or can be provided by the servers and/or services ofmultiple different buyers or enterprises.

In the illustrated example, the server(s) 2904 can include one or moreprocessors 2928, one or more computer-readable media 2930, one or moreI/O devices 2932, and one or more communication interfaces 2934. Eachprocessor 2928 can be a single processing unit or a number of processingunits, and can include single or multiple computing units or multipleprocessing cores. The processor(s) 2928 can be implemented as one ormore microprocessors, microcomputers, microcontrollers, digital signalprocessors, central processing units, state machines, logic circuitries,and/or any devices that manipulate signals based on operationalinstructions. For example, the processor(s) 2928 can be one or morehardware processors and/or logic circuits of any suitable typespecifically programmed or configured to execute the algorithms andprocesses described herein. The processor(s) 2928 can be configured tofetch and execute computer-readable instructions stored in thecomputer-readable media 2930, which can program the processor(s) 2928 toperform the functions described herein.

The computer-readable media 2930 can include volatile and nonvolatilememory and/or removable and non-removable media implemented in any typeof technology for storage of data, such as computer-readableinstructions, data structures, program modules, or other data. Suchcomputer-readable media 2930 can include, but is not limited to, RAM,ROM, EEPROM, flash memory or other memory technology, optical storage,solid state storage, magnetic tape, magnetic disk storage, RAID storagesystems, storage arrays, network attached storage, storage areanetworks, cloud storage, or any other medium that can be used to storethe desired data and that can be accessed by a computing device.Depending on the configuration of the server(s) 2904, thecomputer-readable media 2930 can be a type of computer-readable storagemedia and/or can be a tangible non-transitory media to the extent thatwhen mentioned, non-transitory computer-readable media exclude mediasuch as energy, carrier signals, electromagnetic waves, and signals perse.

The computer-readable media 2930 can be used to store any number offunctional components that are executable by the processor(s) 2928. Inmany implementations, these functional components comprise instructionsor programs that are executable by the processors 2928 and that, whenexecuted, specifically configure the one or more processors 2928 toperform the actions attributed above to the service provider 412 and/orpayment processing service. Functional components stored in thecomputer-readable media 2930 can optionally include a merchant component2936, a buyer component 2937, an application management component 2938,a context determination component 2940, a training component 2942, andone or more other components and data 2944.

Functionality associated with the merchant component 2936, the buyercomponent 2937, the application management component 2938, the contextdetermination component 2940, which can correspond to the merchantcomponent 112, the buyer component 113, the application managementcomponent 114, and the context determination component 116 of FIG. 1,are described above with reference to FIG. 1. The training component2942 can be configured to train models using machine-learningmechanisms. For example, a machine-learning mechanism can analyzetraining data to train a data model that generates an output, which canbe a recommendation, a score, and/or another indication.Machine-learning mechanisms can include, but are not limited tosupervised learning algorithms (e.g., artificial neural networks,Bayesian statistics, support vector machines, decision trees,classifiers, k-nearest neighbor, etc.), unsupervised learning algorithms(e.g., artificial neural networks, association rule learning,hierarchical clustering, cluster analysis, etc.), semi-supervisedlearning algorithms, deep learning algorithms, etc.), statisticalmodels, etc. In at least one example, machine-trained data models can bestored in a data store associated with the user computing device(s) 2902and/or the server(s) 2904 for use at a time after the data models havebeen trained (e.g., at runtime).

The one or more other components and data 2944 can include programs,drivers, etc., and the data used or generated by the functionalcomponents. Further, the server(s) 2904 can include many other logical,programmatic and physical components, of which those described above aremerely examples that are related to the discussion herein.

The one or more “components” referenced herein may be implemented asmore components or as fewer components, and functions described for thecomponents may be redistributed depending on the details of theimplementation. The term “component,” as used herein, refers broadly tosoftware stored on non-transitory storage medium (e.g., volatile ornon-volatile memory for a computing device), hardware, or firmware (orany combination thereof) components. Components are typically functionalsuch that they that may generate useful data or other output usingspecified input(s). A component may or may not be self-contained. Anapplication program (also called an “application”) may include one ormore components, or a component may include one or more applicationprograms that can be accessed over a network or downloaded as softwareonto a device (e.g., executable code causing the device to perform anaction). In additional and/or alternative examples, the component(s) maybe implemented as computer-readable instructions, various datastructures, and so forth via at least one processing unit to configurethe computing device(s) described herein to execute instructions and toperform operations as described herein.

In some examples, a module may include one or more applicationprogramming interfaces (APIs) to perform some or all of itsfunctionality (e.g., operations). In at least one example, a softwaredeveloper kit (SDK) can be provided by the service provider to allowthird-party developers to include service provider functionality and/oravail service provider services in association with their ownthird-party applications. Additionally or alternatively, in someexamples, the service provider can utilize a SDK to integratethird-party service provider functionality into its applications. Thatis, API(s) and/or SDK(s) can enable third-party developers to customizehow their respective third-party applications interact with the serviceprovider or vice versa.

The computer-readable media 2930 can additionally include an operatingsystem 2946 for controlling and managing various functions of theserver(s) 2904.

The communication interface(s) 2934 can include one or more interfacesand hardware components for enabling communication with various otherdevices, such as over the network(s) 2906 or directly. For example,communication interface(s) 2934 can enable communication through one ormore network(s) 2906, which can include, but are not limited any type ofnetwork known in the art, such as a local area network or a wide areanetwork, such as the Internet, and can include a wireless network, suchas a cellular network, a local wireless network, such as Wi-Fi and/orclose-range wireless communications, such as Bluetooth®, BLE, NFC, RFID,a wired network, or any other such network, or any combination thereof.Accordingly, network(s) 2906 can include both wired and/or wirelesscommunication technologies, including Bluetooth®, BLE, Wi-Fi andcellular communication technologies, as well as wired or fiber optictechnologies. Components used for such communications can depend atleast in part upon the type of network, the environment selected, orboth. Protocols for communicating over such networks are well known andwill not be discussed herein in detail.

The server(s) 2904 can further be equipped with various I/O devices2932. Such I/O devices 2932 can include a display, various userinterface controls (e.g., buttons, joystick, keyboard, mouse, touchscreen, biometric or sensory input devices, etc.), audio speakers,connection ports and so forth.

In at least one example, the system 2900 can include a data store 2948that can be configured to store data that is accessible, manageable, andupdatable. In some examples, the data store 2948 can be integrated withthe user computing device 2902 and/or the server(s) 2904. In otherexamples, as shown in FIG. 29, the data store 2948 can be locatedremotely from the server(s) 2904 and can be accessible to the server(s)2904. The data store 2948 can comprise multiple databases and/or serversconnected locally and/or remotely via the network(s) 2906. In at leastone example, the data store(s) 2948 can correspond to the data store(s)118 described above with reference to FIG. 1. As described above, thedata store(s) 2948 can store user profiles, which can include merchantprofiles, buyer profiles, and so on. Furthermore, in at least oneexample, the data store(s) 2948 can store inventory database(s) and/orcatalog database(s). As described above, an inventory can store dataassociated with a quantity of each item that a merchant has available tothe merchant. Furthermore, a catalog can store data associated withitems that a merchant has available for acquisition. The data store(s)2948 can store additional or alternative types of data as describedherein, including but not limited to, applications.

The phrases “in some examples,” “according to various examples,” “in theexamples shown,” “in one example,” “in other examples,” “variousexamples,” “some examples,” and the like generally mean the particularfeature, structure, or characteristic following the phrase is includedin at least one example of the present invention, and may be included inmore than one example of the present invention. In addition, suchphrases do not necessarily refer to the same examples or to differentexamples.

If the specification states a component or feature “can,” “may,”“could,” or “might” be included or have a characteristic, thatparticular component or feature is not required to be included or havethe characteristic.

Further, the aforementioned description is directed to devices andapplications that are related to payment technology. However, it will beunderstood, that the technology can be extended to any device andapplication. Moreover, techniques described herein can be configured tooperate irrespective of the kind of payment object reader, POS terminal,web applications, mobile applications, POS topologies, payment cards,computer networks, and environments.

Various figures included herein are flowcharts showing example methodsinvolving techniques as described herein. The methods illustrated aredescribed with reference to FIGS. 28 and 29 for convenience and ease ofunderstanding. However, the methods illustrated are not limited to beingperformed using components described in FIGS. 28 and 29, and suchcomponents are not limited to performing the methods illustrated herein.

Furthermore, the methods described above are illustrated as collectionsof blocks in logical flow graphs, which represent sequences ofoperations that can be implemented in hardware, software, or acombination thereof. In the context of software, the blocks representcomputer-executable instructions stored on one or more computer-readablestorage media that, when executed by processor(s), perform the recitedoperations. Generally, computer-executable instructions includeroutines, programs, objects, components, data structures, and the likethat perform particular functions or implement particular abstract datatypes. The order in which the operations are described is not intendedto be construed as a limitation, and any number of the described blockscan be combined in any order and/or in parallel to implement theprocesses. In some examples, one or more blocks of the process can beomitted entirely. Moreover, the methods can be combined in whole or inpart with each other or with other methods.

Example Clauses

A. A method comprising: storing applications in a repository associatedwith one or more computing devices of a service provider, whereinindividual of the applications are associated with one or more partsthat are accessible as one or more instant applications, and whereineach instant application of the one or more instant applications isassociated with a particular, discrete functionality; determining, bythe one or more computing devices, context data associated with a usercomputing device; selecting, by the one or more computing devices andbased at least in part on the context data, an instant application ofthe one or more instant applications to be surfaced on the usercomputing device; and causing, by the one or more computing devices, auser interface associated with the instant application to be presentedvia the user computing device, wherein the user interface enables a userof the user computing device to input data for enabling the particular,discrete functionality associated with the instant application, andwherein a portion of the context data is used to customize the userinterface for the user.

B. The method as clause A recites, further comprising: selecting, basedat least in part on the context data, at least one other instantapplication of the one or more instant applications to be surfaced onthe user computing device; determining a sequence for surfacing theinstant application and the at least one other instant application; andcausing the user interface associated with the instant application andanother user interface associated with the other instant application tobe presented based at least in part on the sequence.

C. The method as clause A or B recites, further comprising: receiving anindication of an interaction with an interactable element associatedwith the instant application; and selecting the instant applicationfurther based at least in part on receiving the indication.

D. The method as any of clauses A-C recites, further comprising, at atime after the user interface is presented, causing the application tobe downloaded on the user computing device, wherein downloading theapplication enables a set of functionalities larger than the particular,discrete functionality associated with the instant application.

E. The method as clause D recites, further comprising: prior to causingthe application to be downloaded on the user computing device,accessing, based at least in part on the input data, user dataassociated with the user; and customizing at least one of theapplication or data presented via the application based at least in parton the user data.

F. The method as clause D or E recites, further comprising: prior tocausing the application to be downloaded on the user computing device,receiving, from the user computing device, a request to download theapplication; based at least in part on receiving the request to downloadthe application, storing data provided via the user interface associatedwith the instant application; and associating the data provided via theuser interface with the application, wherein the data provided via theuser interface is accessible via the application after the applicationhas been downloaded on the user computing device.

G. A system comprising: one or more processors; and one or morecomputer-readable media that, when executed by the one or moreprocessors, cause the system to perform operations comprising: storingone or more applications in a repository associated with a serviceprovider, wherein at least a part of an application of the one or moreapplications is associated with a particular, discrete functionality;determining context data associated with a user computing device;selecting, based at least in part on the context data, the applicationfrom the one or more applications, wherein at least the part of theapplication is to be surfaced on the user computing device; and causinga user interface associated with at least the part of the application tobe presented via the user computing device, wherein the user interfaceenables a user of the user computing device to input data for enablingthe particular, discrete functionality, and wherein a portion of thecontext data is used to customize the user interface for the user.

H. The system as clause G recites, the operations further comprising:receiving, from the application, an authorization request to authorizeaccess to data stored in association with the system; and causing atleast a portion of the data stored in association with the system to besurfaced via the user interface.

I. The system as clause G or H recites, the operations furthercomprising: generating an interactable element associated with at leastthe part of the application; and selecting the application further basedat least in part on receiving, from the user computing device, anindication of an interaction with the interactable element.

J. The system as any of clauses G-I recites, the operations furthercomprising: accessing, in the repository and based at least in part onan identifier associated with the user computing device, user dataassociated with the user; and customizing the user interface furtherbased at least in part on the user data.

K. The system as any of clauses G-J recites, the operations furthercomprising: receiving, over a period of time, location data associatedwith the user computing device, wherein at least a portion of thecontext data is based at least in part on the location data; andselecting the application further based at least in part on determiningthat a location of the user computing device is proximate to an entityassociated with the application.

L. The system as any of clauses G-K recites, the operations furthercomprising, wherein at least a portion of the context data is associatedwith an indication of a wait time associated with the user computingdevice, the operations further comprising causing the user interfaceassociated with at least the part of the application to be presented viathe user computing device based at least in part on the wait time.

M. The system as any of clauses G-L recites, wherein the user interfaceassociated with at least the part of the application is only associatedwith the part of the application, which is associated with an instantapplication having fewer functionalities than the application, theoperations further comprising causing the application to be downloadedon to the user computing device at a time after the user interface ispresented.

N. One or more computer-readable media that, when executed by one ormore processors, cause the one or more processors to perform operationscomprising: storing one or more applications in a repository associatedwith a service provider, wherein at least a part of an application ofthe one or more applications is associated with a particular, discretefunctionality; determining context data associated with a user computingdevice; selecting, based at least in part on the context data, theapplication from the one or more applications, wherein at least the partof the application is to be surfaced on the user computing device; andcausing a user interface associated with at least the part of theapplication to be presented via the user computing device, wherein theuser interface enables a user of the user computing device to input datafor enabling the particular, discrete functionality, and wherein aportion of the context data is used to customize the user interface forthe user.

O. The one or more computer-readable media of clause N, the operationsfurther comprising: accessing data associated with at least one of anentity associated with the application or the user; and customizing atleast one of the application, the part of the application, or datapresented via the user interface based at least in part on the data.

P. The one or more computer-readable media of clause N or O, theoperations further comprising: generating an interactable elementassociated with at least the part of the application; associating theinteractable element with one or more other interactable elementsassociated with one or more other parts of at least one of theapplication or another application to generate a multi-functioninteractable element; receiving, from the user computing device, anindication of an interaction with the multi-function interactableelement; and determining, based at least in part on the context data, tocause the user interface associated with at least the part of theapplication to be presented prior to causing one or more other userinterfaces associated with the one or more other parts of at least oneof the application or another application associated with themulti-function interactable element to be presented.

Q. The one or more computer-readable media of any of clauses N-P,wherein the particular, discrete functionality is associated with addinginventory to an inventory database associated with the service provider.

R. The one or more computer-readable media of any of clauses N-Q,wherein the particular, discrete functionality is associated with atleast one of ordering one or more stored balance cards or associatingfunds with a stored balance card.

S. The one or more computer-readable media of any of clauses N-R,wherein the particular, discrete functionality is associated withredeeming loyalty in association with a transaction to be processed bythe service provider.

T. The one or more computer-readable media of any of clauses N-S,wherein the particular, discrete functionality is associated with atleast one of clocking in for a shift, clocking out of a shift, orinputting gratuity associated with a shift.

U. A computer-implemented method comprising: detecting engagement withan option from within a first instant application on a user computingdevice, wherein the first instant application is associated with a firstparticular, discrete functionality; triggering a second instantapplication to be initialized in response to the engagement, wherein thesecond instant application is associated with a second particular,discrete functionality; transitioning provisionally from the firstinstant application to the second instant application to allow access tothe second particular, discrete functionality associated with the secondinstant application; receiving an indication of a user interaction withthe second instant application; embedding a portion of the userinteraction in the first instant application; and presenting theembedded portion of the user interaction on a user interface associatedwith the first instant application via the user computing device.

V. The computer-implemented method as clause U recites, wherein thefirst instant application is associated with an application, theapplication being associated with a set of functionalities larger thanthe first particular, discrete functionality associated with the firstinstant application.

W. The computer-implemented method as clause V recites, furthercomprising, at a time after the portion of the user interaction isembedded into the first instant application, causing the application tobe downloaded onto the user computing device, wherein the portion of theuser interaction embedded in the first instant application is embeddedin the application.

X. The computer-implemented method as any of clauses U-W recites,wherein the first particular, discrete functionality is associated witha buyer application and enables payment via the buyer application andthe second particular, discrete functionality is associated with amerchant application and enables building of a virtual cart.

Y. The computer-implemented method as clause X recites, wherein thebuyer application is a peer-to-peer payment application.

Z. The computer-implemented method as any of clauses U-Y recites,wherein the first particular, discrete functionality is associated witha waitlist tracking functionality provided by a merchant application andthe second particular, discrete functionality is associated with anordering functionality provided by the merchant application.

AA. The computer-implemented method as any of clauses U-Z recites,further comprising: generating an interactable element associated withthe first instant application; and providing the first instantapplication to the user computing device based at least in part onreceiving, from the user computing device, an indication of aninteraction with the interactable element.

AB. The computer-implemented method as any of clauses U-AA recites,wherein the second instant application is initialized without furtherinput from the user.

AC. A system comprising: one or more processors; and one or morecomputer-readable media that, when executed by the one or moreprocessors, cause the system to perform operations comprising: detectingengagement with a first application; triggering a second application tobe initialized in response to the engagement; transitioningprovisionally from the first application to the second application;receiving an indication of a user interaction with the secondapplication; embedding a portion of the user interaction in the firstapplication; and presenting the embedded portion of the user interactionon a user interface associated with the first application via a usercomputing device.

AD. The system as clause AC recites, wherein the first application isassociated with a first particular, discrete functionality, and whereinthe first particular, discrete functionality is associated with aninstant application, the first application being associated with a setof functionalities larger than the first particular, discretefunctionality associated with the instant application, and wherein theengagement with the first application is with the instant application.

AE. The system as clause AD recites, wherein the first particular,discrete functionality is availed via a partial download of the firstapplication, the operations further comprising, at a time after theportion of the user interaction is embedded in the first application,causing the first application to be downloaded completely onto the usercomputing device.

AF. The system as clause AD or AE recites, wherein the first applicationis a buyer application and the first particular, discrete functionalityenables payment via the buyer application and the second application isa merchant application, wherein the merchant application is associatedwith a second particular, discrete functionality that enables buildingof a virtual cart, and wherein the user interaction is with the secondparticular, discrete functionality.

AG. The system as any of clauses AD-AF recites, wherein the firstparticular, discrete functionality is associated with a waitlisttracking functionality and the second application is associated with asecond particular, discrete functionality that is associated with anordering functionality, and wherein the user interaction is with thesecond particular, discrete functionality.

AH. The system as any of clauses AC-AG recites, wherein the firstapplication and the second application are associated with differentservice providers.

AI. One or more computer-readable media that, when executed by one ormore processors, cause the one or more processors to perform operationscomprising: detecting engagement with a first application; triggering asecond application to be initialized in response to the engagement;transitioning provisionally from the first application to the secondapplication; receiving an indication of a user interaction with thesecond application; embedding a portion of the user interaction in thefirst application; and presenting the embedded portion of the userinteraction on a user interface associated with the first applicationvia a user computing device.

AJ. The one or more computer-readable media as clause AI recites,wherein the first application is associated with a first particular,discrete functionality, and wherein the first particular, discretefunctionality is associated with an instant application, the firstapplication being associated with a set of functionalities larger thanthe first particular, discrete functionality associated with the instantapplication, and wherein the engagement with the first application iswith the instant application.

AK. The one or more computer-readable media as clause AJ recites,wherein the first particular, discrete functionality is availed via apartial download of the first application, the operations furthercomprising, at a time after the portion of the user interaction isembedded in the first application, causing the first application to bedownloaded completely onto the user computing device.

AL. The one or more computer-readable media as clause AJ or AK recites,wherein the first application is a buyer application and the firstparticular, discrete functionality enables payment via the buyerapplication and the second application is a merchant application,wherein the merchant application is associated with a second particular,discrete functionality associated with an online store of a merchantassociated with the merchant application, and wherein the userinteraction is with the second particular, discrete functionality.

AM. The one or more computer-readable media as any of clauses AJ-ALrecites, wherein the first application is a merchant application and thefirst particular, discrete functionality enables building of a virtualcart, and the second application is a buyer application, wherein thebuyer application enables payment for one or more items associated withthe virtual cart, and wherein the user interaction is with the secondparticular, discrete functionality.

AN. The one or more computer-readable media as any of clauses AJ-AMrecites, wherein the first particular, discrete functionality isassociated with a waitlist tracking functionality and the secondapplication is associated with a second particular, discretefunctionality that is associated with an ordering functionality, andwherein the user interaction is with the second particular, discretefunctionality.

AO. A method, implemented at least in part by one or more computingdevices associated with a service provider, the method comprising:causing a first user interface associated with an instant applicationassociated with a particular, discrete functionality of an applicationto be presented via a first user computing device of a user; receivingdata via an interaction with the first user interface associated withthe instant application; receiving a request to download the applicationfrom a second user computing device of the user; causing the applicationto be downloaded on the second user computing device of the user; andcausing the data received via the interaction with the first userinterface associated with the instant application to be presented via asecond user interface associated with the application on the second usercomputing device, wherein the data is presented via the second userinterface based at least in part on device characteristics of the seconduser computing device.

AP. The method as clause AO recites, wherein the application isassociated with a set of functionalities that is larger than theparticular, discrete functionality of the instant application.

AQ. The method as clause AO or AP recites, further comprising:generating an interactable element associated with the instantapplication; and causing the first user interface to be presented basedat least in part on receiving, from the first user computing device, anindication of an interaction with the interactable element.

AR. The method as clause AQ recites, wherein the interactable element isassociated with at least one of a physical mailer, a push notification,an email, or a text message.

AS. The method as any of clauses AO-AR recites, further comprising:determining context data associated with the first user computing deviceof the user; and causing the first user interface associated with theinstant application to be presented via the first user computing deviceof the user based at least in part on the context data.

AT. The method as any of clauses AO-AS recites, further comprising:based at least in part on receiving the request to download theapplication from the second user computing device of the user, storingsession data received via a session associated with the instantapplication, wherein the session data includes the data received via theinteraction with the first user interface; sending the session data tothe second user computing device of the user; and customizing the seconduser interface based at least in part on the session data.

AU. A system comprising: one or more processors; and one or morecomputer-readable media that, when executed by the one or moreprocessors, cause the system to perform operations comprising: causing afirst user interface associated with an instant application associatedwith a particular, discrete functionality of an application to bepresented via a first user computing device of a user; receiving datavia an interaction with the first user interface associated with theinstant application; receiving a request to download the applicationfrom a second user computing device of the user; causing the applicationto be downloaded on the second user computing device of the user; andcausing the data received via the interaction with the first userinterface associated with the instant application to be associated withthe application on the second user computing device.

AV. The system as clause AU recites, wherein the data is associated withsession data of a session of the instant application.

AW. The system as clause AU or AV recites, the operations furthercomprising: generating an interactable element associated with theinstant application, wherein the interactable element is associated witha first identifier of the user; and causing the first user interface tobe presented based at least in part on receiving, from the first usercomputing device, an indication of an interaction with the interactableelement, wherein the data is associated with the first identifier.

AX. The system as clause AW recites, wherein the request is associatedwith a second identifier, the operations further comprising: determiningthat the first identifier and the second identifier are associated witha same user; determining a correspondence between the first usercomputing device and the second user computing device based at least inpart on determining that the first identifier and the second identifierare associated with the same user; based at least in part on determiningthe correspondence between the first user computing device and thesecond user computing device, storing session data received via asession associated with the instant application, wherein the sessiondata includes the data received via the interaction with the first userinterface; sending the session data to the second user computing deviceof the user; and customizing at least one of the application or datapresented via a second user interface associated with the applicationbased at least in part on the session data.

AY. The system as any of clauses AU-AX recites, the operations furthercomprising: determining first location data associated with the firstuser computing device; determining second location data associated withthe second user computing device; determining, based at least in part onthe first location data and the second location data, that the firstuser computing device is within a threshold distance of the second usercomputing device; determining a correspondence between the first usercomputing device and the second user computing device based at least inpart on determining that the first user computing device is within athreshold distance of the second user computing device; based at leastin part on determining the correspondence between the first usercomputing device and the second user computing device, storing sessiondata received via a session associated with the instant application,wherein the session data includes the data received via the interactionwith the first user interface; sending the session data to the seconduser computing device of the user; and customizing at least one of theapplication or data presented via a second user interface associatedwith the application based at least in part on the session data.

AZ. The system as any of clauses AU-AY recites, wherein the data isassociated with first identification data associated with the user, andwherein the request is associated with second identification data, theoperations further comprising: determining that the first identificationdata corresponds with the second identification data; determining acorrespondence between the first user computing device and the seconduser computing device based at least in part on determining that thefirst identification data corresponds with the second identificationdata; based at least in part on determining the correspondence betweenthe first user computing device and the second user computing device,storing session data received via a session associated with the instantapplication, wherein the session data includes the data received via theinteraction with the first user interface; sending the session data tothe second user computing device of the user; and customizing at leastone of the application or data presented via a second user interfaceassociated with the application based at least in part on the sessiondata.

BA. The system as clause AZ recites, wherein the first identificationdata comprises at least one of an account number, a physical address, atelephone number, or an email address associated with the user andwherein the second identification data comprises at least one of theaccount number, the physical address, the telephone number, or the emailaddress associated with the user.

BB. The system as any of clauses AU-BA recites, the operations furthercomprising: determining context data associated with the first usercomputing device of the user; and causing the first user interfaceassociated with the instant application to be presented via the firstuser computing device of the user based at least in part on the contextdata.

BC. One or more computer-readable media that, when executed by one ormore processors, cause the one or more processors to perform operationscomprising: causing a first user interface associated with an instantapplication associated with a particular, discrete functionality of anapplication to be presented via a first user computing device of a user;receiving data via an interaction with the first user interfaceassociated with the instant application; receiving a request to downloadthe application from a second user computing device of the user; causingthe application to be downloaded on the second user computing device ofthe user; and causing the data received via the interaction with thefirst user interface associated with the instant application to beassociated with the application on the second user computing device.

BD. The one or more computer-readable media as clause BC recites,wherein the application is associated with a set of functionalities thatis larger than the particular, discrete functionality of the instantapplication.

BE. The one or more computer-readable media as clause BC or BD recites,the operations further comprising: generating an interactable elementassociated with the instant application; and causing the first userinterface to be presented based at least in part on receiving anindication of an interaction with the interactable element via the firstuser computing device of the user.

BF. The one or more computer-readable media as any of clauses BC-BErecites, the operations further comprising: determining a first devicecharacteristic associated with the first user computing device, whereinthe first user interface is presented based at least in part on thefirst device characteristic; and determining a second devicecharacteristic associated with the second user computing device, whereina second user interface associated with the application is presented,via the second user computing device based at least in part on thesecond device characteristic.

BG. The one or more computer-readable media as any of clauses BC-BFrecites, wherein the instant application is associated with ademonstration of functionality of the application.

BH. The one or more computer-readable media as any of clauses BC-BGrecites, wherein the instant application is associated with a payment.

BI. A computer-implemented method comprising: detecting engagement withan option from within a buyer application on a computing device of abuyer; triggering an instant application associated with a merchant tobe initialized in response to the engagement, wherein the instantapplication is associated with a particular, discrete functionality of amerchant application of the merchant; transitioning from the buyerapplication to the instant application to allow access to theparticular, discrete functionality associated with the instantapplication; receiving, from the instant application, an indication of atransaction between the merchant and the buyer for processing payment ofthe transaction via the buyer application; and associating theindication of the transaction with stored activity data of one or moretransactions of the buyer, wherein the one or more transactions areassociated with the buyer application.

BJ. The computer-implemented method as clause BI recites, wherein thebuyer application is a peer-to-peer payment application.

BK. The computer-implemented method as clause BI or BJ recites, whereinthe option is associated with a user interface of the buyer applicationthat includes a plurality of options associated with a plurality ofmerchants.

BL. The computer-implemented method as clause BK recites, wherein theuser interface is an activity user interface of the buyer applicationthat presents at least a portion of the stored activity data.

BM. The computer-implemented method as clause BL recites, whereinindividual of the plurality of options are associated with individual ofthe one or more transactions.

BN. The computer-implemented method as any of clauses BI-BM recites,wherein the merchant application is associated with a set offunctionalities that is larger than the particular, discretefunctionality of the instant application.

BO. The computer-implemented method as any of clauses BI-BN recites,wherein the buyer application and the merchant application areassociated with a same service provider.

BP. The computer-implemented method as any of clauses BI-BO recites,wherein the buyer application is associated with a first serviceprovider and the merchant application is associated with a secondservice provider that is different than the first service provider, andwherein the merchant application is integrated with the buyerapplication via an application programming interface.

BQ. A system comprising: one or more processors; and one or morecomputer-readable media that, when executed by the one or moreprocessors, cause the system to perform operations comprising: detectingengagement with a buyer application on a computing device of a buyer;triggering a particular, discrete functionality of a merchantapplication of the merchant to be initialized in response to theengagement; accessing, from the buyer application, the merchantapplication to allow access to the particular, discrete functionalityassociated with the merchant application; and receiving an indication ofa transaction between the merchant and the buyer, wherein the indicationof the transaction is associated with stored activity data of one ormore transactions of the buyer, wherein the one or more transactions areassociated with the buyer application.

BR. The system as clause BQ recites, wherein the particular, discretefunctionality is associated with an instant application embedded in thebuyer application, and wherein the merchant application is associatedwith a larger set of functionalities than the particular, discretefunctionality.

BS. The system as clause BQ or BR recites, wherein the engagement iswith an option that is associated with a user interface of the buyerapplication that includes a plurality of options associated with aplurality of merchants.

BT. The system as any of clauses BQ-BS recites, wherein the engagementis with an option that is associated with a user interface of the buyerapplication that includes a plurality of options, wherein each option ofthe plurality of options points to an embedded application associatedwith a corresponding merchant of a plurality of merchants.

BU. The system as clause BT recites, wherein individual of the pluralityof options are associated with individual of the one or moretransactions associated with the buyer application.

BV. The system as clause BT or BU recites, wherein a transaction of theone or more transactions is awaiting fulfillment, and wherein aparticular option associated with the transaction is associated withtracking data associated with fulfillment.

BW. The system as any of clauses BQ-BV recites, wherein the indicationis received from one or more server computing devices associated withthe buyer application and the indication indicates that payment for thetransaction has been processed by the one or more server computingdevices.

BX. The system as any of clauses BQ-BW recites, wherein the indicationis received from the merchant application and indicates that payment forthe transaction was processed via buyer application functionalityembedded in the merchant application.

BY. One or more computer-readable media that, when executed by one ormore processors, cause the one or more processors to perform operationscomprising: detecting engagement with a buyer application on a computingdevice of a buyer; triggering a particular, discrete functionality of amerchant application of the merchant to be initialized in response tothe engagement; transitioning from the buyer application to the merchantapplication to allow access to the particular, discrete functionalityassociated with the merchant application; and receiving an indication ofa transaction between the merchant and the buyer, wherein the indicationof the transaction is associated with stored activity data of one ormore transactions of the buyer, wherein the one or more transactions areassociated with the buyer application.

BZ. The one or more computer-readable media as clause BY recites,wherein the particular, discrete functionality is associated with aninstant application embedded in the buyer application, and wherein themerchant application is associated with a larger set of functionalitiesthan the particular, discrete functionality.

CA. The one or more computer-readable media as clause BY or BZ recites,wherein the indication indicates that payment for the transaction hasbeen processed by one or more server computing devices associated withthe buyer application.

CB. The one or more computer-readable media as any of clauses BY-CArecites, wherein the indication indicates that payment for thetransaction was processed via buyer application functionality embeddedin the merchant application.

While the example clauses described above are described with respect toone particular implementation, it should be understood that, in thecontext of this document, the content of the example clauses can also beimplemented via a method, device, system, a computer-readable medium,and/or another implementation. Additionally, any of examples A-CB may beimplemented alone or in combination with any other one or more of theexamples A-CB.

What is claimed is:
 1. A method comprising: storing applications in arepository associated with one or more computing devices of a serviceprovider, wherein individual of the applications are associated with oneor more parts that are accessible as one or more instant applications,and wherein each instant application of the one or more instantapplications is associated with a particular, discrete functionality;determining, by the one or more computing devices, context dataassociated with a user computing device; selecting, by the one or morecomputing devices and based at least in part on the context data, aninstant application of the one or more instant applications to besurfaced on the user computing device; and causing, by the one or morecomputing devices, a user interface associated with the instantapplication to be presented via the user computing device, wherein theuser interface enables a user of the user computing device to input datafor enabling the particular, discrete functionality associated with theinstant application, and wherein a portion of the context data is usedto customize the user interface for the user.
 2. The method as claim 1recites, further comprising: selecting, based at least in part on thecontext data, at least one other instant application of the one or moreinstant applications to be surfaced on the user computing device;determining a sequence for surfacing the instant application and the atleast one other instant application; and causing the user interfaceassociated with the instant application and another user interfaceassociated with the other instant application to be presented based atleast in part on the sequence.
 3. The method as claim 1 recites, furthercomprising: receiving an indication of an interaction with aninteractable element associated with the instant application; andselecting the instant application further based at least in part onreceiving the indication.
 4. The method as claim 1 recites, furthercomprising, at a time after the user interface is presented, causing theapplication to be downloaded on the user computing device, whereindownloading the application enables a set of functionalities larger thanthe particular, discrete functionality associated with the instantapplication.
 5. The method as claim 4 recites, further comprising: priorto causing the application to be downloaded on the user computingdevice, accessing, based at least in part on the input data, user dataassociated with the user; and customizing at least one of theapplication or data presented via the application based at least in parton the user data.
 6. The method as claim 4 recites, further comprising:prior to causing the application to be downloaded on the user computingdevice, receiving, from the user computing device, a request to downloadthe application; based at least in part on receiving the request todownload the application, storing data provided via the user interfaceassociated with the instant application; and associating the dataprovided via the user interface with the application, wherein the dataprovided via the user interface is accessible via the application afterthe application has been downloaded on the user computing device.
 7. Asystem comprising: one or more processors; and one or morecomputer-readable media that, when executed by the one or moreprocessors, cause the system to perform operations comprising: storingone or more applications in a repository associated with a serviceprovider, wherein at least a part of an application of the one or moreapplications is associated with a particular, discrete functionality;determining context data associated with a user computing device;selecting, based at least in part on the context data, the applicationfrom the one or more applications, wherein at least the part of theapplication is to be surfaced on the user computing device; and causinga user interface associated with at least the part of the application tobe presented via the user computing device, wherein the user interfaceenables a user of the user computing device to input data for enablingthe particular, discrete functionality, and wherein a portion of thecontext data is used to customize the user interface for the user. 8.The system as claim 7 recites, the operations further comprising:receiving, from the application, an authorization request to authorizeaccess to data stored in association with the system; and causing atleast a portion of the data stored in association with the system to besurfaced via the user interface.
 9. The system as claim 7 recites, theoperations further comprising: generating an interactable elementassociated with at least the part of the application; and selecting theapplication further based at least in part on receiving, from the usercomputing device, an indication of an interaction with the interactableelement.
 10. The system as claim 7 recites, the operations furthercomprising: accessing, in the repository and based at least in part onan identifier associated with the user computing device, user dataassociated with the user; and customizing the user interface furtherbased at least in part on the user data.
 11. The system as claim 7recites, the operations further comprising: receiving, over a period oftime, location data associated with the user computing device, whereinat least a portion of the context data is based at least in part on thelocation data; and selecting the application further based at least inpart on determining that a location of the user computing device isproximate to an entity associated with the application.
 12. The systemas claim 7 recites, the operations further comprising, wherein at leasta portion of the context data is associated with an indication of a waittime associated with the user computing device, the operations furthercomprising causing the user interface associated with at least the partof the application to be presented via the user computing device basedat least in part on the wait time.
 13. The system as claim 7 recites,wherein the user interface associated with at least the part of theapplication is only associated with the part of the application, whichis associated with an instant application having fewer functionalitiesthan the application, the operations further comprising causing theapplication to be downloaded on to the user computing device at a timeafter the user interface is presented.
 14. One or more computer-readablemedia that, when executed by one or more processors, cause the one ormore processors to perform operations comprising: storing one or moreapplications in a repository associated with a service provider, whereinat least a part of an application of the one or more applications isassociated with a particular, discrete functionality; determiningcontext data associated with a user computing device; selecting, basedat least in part on the context data, the application from the one ormore applications, wherein at least the part of the application is to besurfaced on the user computing device; and causing a user interfaceassociated with at least the part of the application to be presented viathe user computing device, wherein the user interface enables a user ofthe user computing device to input data for enabling the particular,discrete functionality, and wherein a portion of the context data isused to customize the user interface for the user.
 15. The one or morecomputer-readable media of claim 14, the operations further comprising:accessing data associated with at least one of an entity associated withthe application or the user; and customizing at least one of theapplication, the part of the application, or data presented via the userinterface based at least in part on the data.
 16. The one or morecomputer-readable media of claim 14, the operations further comprising:generating an interactable element associated with at least the part ofthe application; associating the interactable element with one or moreother interactable elements associated with one or more other parts ofat least one of the application or another application to generate amulti-function interactable element; receiving, from the user computingdevice, an indication of an interaction with the multi-functioninteractable element; and determining, based at least in part on thecontext data, to cause the user interface associated with at least thepart of the application to be presented prior to causing one or moreother user interfaces associated with the one or more other parts of atleast one of the application or another application associated with themulti-function interactable element to be presented.
 17. The one or morecomputer-readable media of claim 14, wherein the particular, discretefunctionality is associated with adding inventory to an inventorydatabase associated with the service provider.
 18. The one or morecomputer-readable media of claim 14, wherein the particular, discretefunctionality is associated with at least one of ordering one or morestored balance cards or associating funds with a stored balance card.19. The one or more computer-readable media of claim 14, wherein theparticular, discrete functionality is associated with redeeming loyaltyin association with a transaction to be processed by the serviceprovider.
 20. The one or more computer-readable media of claim 14,wherein the particular, discrete functionality is associated with atleast one of clocking in for a shift, clocking out of a shift, orinputting gratuity associated with a shift.